cvs commit: src/lib/libutil Makefile libutil.h pidfile.3 pidfile.c

[Scott Long]

David O'Brien wrote:
> On Thu, Aug 25, 2005 at 08:43:54AM -0700, John-Mark Gurney wrote:
> 
>>Robert Watson wrote this message on Thu, Aug 25, 2005 at 06:05 +0100:
>>
>>>On Wed, 24 Aug 2005, Pawel Jakub Dawidek wrote:
>>>
>>>
>>>>pjd         2005-08-24 17:21:38 UTC
>>>>
>>>>FreeBSD src repository
>>>>
>>>>Modified files:
>>>>  lib/libutil          Makefile libutil.h
>>>>Added files:
>>>>  lib/libutil          pidfile.3 pidfile.c
>>>>Log:
>>>>Add a family of functions for reliable pidfiles handling.
>>>>
>>>>Idea from:      jmg
>>>>Discussed on:   arch@
>>>
>>>Something I'd very much like to see is for daemon pid files to start being 
>>>placed in /var/run/<daemon>/<daemon>.pid, as opposed to directly in 
>>>/var/run.  This will allow us to set specific ownership on the parent 
>>>directory for a pid file, so that privilege is not required to write out a 
>>>pid file in a safe place.
> 
> 
> Yuck!  Directory hell to find information.
>  
> 
>>why not add an rc.subr option to precreate the file with the correct
>>user?  I was running up conserver, and I decided to run it as a seperate
>>user, and since I created it as owned by the conserver user, conserver
>>just opened and wrote to the file..
>>just a thought...
> 
> 
> I like this thought better and feel its more along traditional ways.
> 

I think that Robert is thinking beyond the traditional user:group 
protection model of Unix and towards the much more powerful and flexible
MAC protection model.

Scott