Date: Mon, 06 Feb 2012 23:18:50 +0400 From: Andrey Zonov <andrey@zonov.org> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org>, Guy Helmer <ghelmer@palisadesystems.com>, svn-src-all@freebsd.org, Mikolaj Golub <trociny@freebsd.org>, svn-src-head@freebsd.org Subject: Re: svn commit: r230869 - head/usr.sbin/daemon Message-ID: <4F30279A.4010307@zonov.org> In-Reply-To: <201202061025.42239.jhb@freebsd.org> References: <201202011641.q11Gf0j6095461@svn.freebsd.org> <1E1FA19C-7C4C-4288-B163-E33FC68D9837@palisadesystems.com> <20120206144337.GH1324@garage.freebsd.pl> <201202061025.42239.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06.02.2012 19:25, John Baldwin wrote: >> >> My expectation is that as long as parent process holds pidfile >> descriptor open and locked, the pidfile should remain locked even after >> fork(2)/execve(2). Worth checking, though. > > Yes, if the daemon process hung around that would work. Note that I think > you would need to do a double-fork for that to work though since users > expect daemon to return instantly and not need to be put in the background. > It would be also nice to have an option for automatically respawn the child. This option has GNU version of daemon. What do you think? -- Andrey Zonov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F30279A.4010307>