/var/run/directory/

[Russell Coker]

On Sat, 2 Oct 2004 14:32, Bill Nottingham <notting at redhat.com> wrote:
> Bill Nottingham (notting at redhat.com) said:
> > Russell Coker (russell at coker.com.au) said:
> > > > Well, it will break parts of the initscripts if it's just done
> > > > in the daemons. :)
> > >
> > > Naturally changes to the daemon, the init scripts for the daemon, and
> > > to the SE Linux policy need to be synchronised.  But apart from that do
> > > you have any problem with the idea?
> >
> > You need to change the generic initscripts as well... they rely
> > on the pid file location.
>
> Moreover, you break the FHS (and therefore, LSB.)

Below is the relevant section of the FHS.  It says that programs which use 
more than one file are encouraged to use a sub-directory (IE Sendmail).  
Doing the same for programs which only have a single file is not a major 
break.

/var/run : Run-time variable data

Purpose

   This directory contains system information data describing the system
   since it was booted. Files under this directory must be cleared
   (removed or truncated as appropriate) at the beginning of the boot
   process. Programs may have a subdirectory of /var/run; this is
   encouraged for programs that use more than one run-time file. [42]
   Process identifier (PID) files, which were originally placed in /etc,
   must be placed in /var/run. The naming convention for PID files is
   <program-name>.pid. For example, the crond PID file is named
   /var/run/crond.pid.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page