Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Oct 2009 19:20:02 GMT
From:      Daniel Feenberg <feenberg@nber.org>
To:        freebsd-doc@FreeBSD.org
Subject:   Re: docs/132260: dhcpd(8) pid not stored in documented location
Message-ID:  <200910221920.n9MJK2D1049004@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/132260; it has been noted by GNATS.

From: Daniel Feenberg <feenberg@nber.org>
To: Josh Paetzel <jpaetzel@FreeBSD.org>
Cc: bug-followup@FreeBSD.org, Giorgos Keramidas <keramida@FreeBSD.org>
Subject: Re: docs/132260: dhcpd(8) pid not stored in documented location
Date: Thu, 22 Oct 2009 14:43:03 -0400 (EDT)

 On Thu, 22 Oct 2009, Josh Paetzel wrote:
 
 > The reason that it puts the pidfile in /var/run/dhcpd is that you are running 
 > with either paranoia or chmodded as the dhcpd user.  In either case it can't 
 > write to /var/run as it starts up as the dhcpd user.
 
 If you say so.
 
 >
 > If you look at the ownership of /var/run/dhcpd you'll see it is owned by 
 > dhcpd:dhcpd
 
 Yes
 
 >
 > If you run as root, or without paranoia it will in fact create the pidfile in 
 > /var/run/
 
 I do run dhcpd as root and without paranoia, so I question this claim. If 
 the daemon changes its uid for security purposes, I have no objection 
 (although there is no mention of this on the man page) but why not fill in 
 /var/run as documented before dropping priviledges?
 
 >
 > I suppose we could patch the man pages depending on the compilation options 
 > or something.
 >
 
 No need for anything so elaborate. You could just add a fourth file path 
 to the list of files used.
 
 Thanks for having a look. It isn't a big deal and I thought I was helping.
 
 Daniel Feenberg
 
 
 > Thanks,
 >
 > Josh Paetzel
 >
 >
 >



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200910221920.n9MJK2D1049004>