Date: Fri, 6 Jan 2012 10:18:29 -0600 From: Guy Helmer <guy.helmer@palisadesystems.com> To: Doug Barton <dougb@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r229667 - head/usr.sbin/daemon Message-ID: <C1CE4875-6FD5-4A3F-AB6A-64C0573C29AE@palisadesystems.com> In-Reply-To: <4F066340.9010507@FreeBSD.org> References: <201201052248.q05MmaZk059871@svn.freebsd.org> <4F066340.9010507@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 5, 2012, at 8:58 PM, Doug Barton wrote: > On 01/05/2012 14:48, Guy Helmer wrote: >> Allow daemon(8) to run pidfile_open() before relenquishing = privileges >> so pid files can be written in /var/run when started as root. >=20 > I'm not sure how useful this is since when daemon is exiting it won't = be > able to remove the pid file (unless I'm missing something). >=20 > Isn't it better to pre-create the pid file with the proper permissions > for the unprivileged user? >=20 Would it be OK for daemon to hang around and wait for the child process = to exit, then remove the pid file? The only other alternative I see would be to create a subdirectory that = is writable by the user so the child can create and delete the pid file. Guy= -------- This message has been scanned by ComplianceSafe, powered by Palisade's PacketSure.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C1CE4875-6FD5-4A3F-AB6A-64C0573C29AE>