On Thu, 15 Jul 2010 16:49:59 +0200
Lennart Poettering <mzerqung(a)0pointer.de> wrote:
On Thu, 15.07.10 15:43, Enrico Scholz
(enrico.scholz(a)informatik.tu-chemnitz.de) wrote:
>
> Bill Nottingham <notting(a)redhat.com> writes:
>
> > I suspect the biggest issue here is confined daemons, as they may
> > not have permissions to create their own directories in /var/run
>
> is this really an issue? upstart (and systemd probably too) work
> best with non forking daemons so that the pidfile hack is not
> needed anymore.
systemd doesn't care about PID files. If daemons still write them it's
fine, but they don't matter.
You are completely disregarding the case an admin starts daemons
manually. Often pid files are checked so that an admin starting a
daemon manually does not make a mess, if the daemon was already running.
I think what's more interesting here is socket creation in
/var/run. i.e. it's the primarily used place to put client
communication sockets of system daemons.
Yes, this is indeed the case, there are daemons that create sockets
in /var/run/<something> and they need to be abel to create those
sockets with the correct permissions and selinux labels
Simo.
--
Simo Sorce * Red Hat, Inc * New York