> > Is there really anyone that can justify the way socket paths are > > created should contain the PID? You clearly saw the problem with it in > > the Windows code base, but yet pushed on to keep it in the Linux one. > > I simply do not see why you're not taking this patch as a way to > > encourage people to migrate towards a saner default, and somewhere > > down the line maybe even switch the default behavior. > > I think that Windows doesn't support getpid(). MSDN documents it that way, > at least. That is probably why we omit it on Windows, though I do not know > for sure. Guru, is that the reason? > Sorry to step in... Windows supports a form of getpid() (https://msdn.microsoft.com/en-us/library/t2y34y40.aspx). On Windows it does not make sense to make our own daemon(service) behavior, because we can simply rely on a common on the service manager (just be subscribing to it), which brings more to the table and users are already used to it.
Most of the daemon code under windows is used just to keep compatibility for unit tests and the ease to maintain them. I hope it brings more light on the subject. Thanks, Alin. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
