[ovs-dev] [PATCH] syslog: Provide stub functions for openlog and syslog.

Ben Pfaff blp at nicira.com
Tue Jan 21 19:26:03 UTC 2014


On Tue, Jan 21, 2014 at 10:11:16AM -0800, Gurucharan Shetty wrote:
> On Tue, Jan 21, 2014 at 10:04 AM, Ben Pfaff <blp at nicira.com> wrote:
> > On Tue, Jan 21, 2014 at 10:02:09AM -0800, Gurucharan Shetty wrote:
> >> On Tue, Jan 7, 2014 at 10:31 AM, Ben Pfaff <blp at nicira.com> wrote:
> >> > On Mon, Jan 06, 2014 at 02:40:34PM -0800, Gurucharan Shetty wrote:
> >> >> One option to implement openlog and syslog functionality in windows
> >> >> is to use windows event logger. But it looks like it involves changing
> >> >> registry settings and in general looks complicated.
> >> >>
> >> >> For the time being, do nothing for syslog. All the information needed for
> >> >> debugging will be present through the 'file' option anyways.
> >> >>
> >> >> We can start OVS daemons on windows with "-vfile:info -vsyslog:off".
> >> >
> >> > This series seems reasonable to me.  Should we also update lib/vlog.man,
> >> > lib/vlog-unixctl.man, and utilities/ovs-appctl.8.in to describe the
> >> > behavior of syslog on Windows?.
> >>
> >> I was dilly-dallying on this a bit as we do not have a ovs-appctl
> >> implementation yet. But, I think it makes sense to add the
> >> documentation now.
> >
> > OK.
> >
> > Should we put some kind of status in BUILD.Windows?
> We cannot yet compile any of the executables upstream cleanly with the
> changes made so far. So a status update just for ovs-appctl in
> BUILD.Windows feels a little odd.

OK, that makes sense.



More information about the dev mailing list