Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Feb 2000 10:20:14 +0200
From:      Sheldon Hearn <sheldonh@uunet.co.za>
To:        Andrey Novikov <novikov@webclub.ru>
Cc:        freebsd-security@FreeBSD.ORG
Subject:   Re: Nonpriveleged daemons and pid files 
Message-ID:  <623.950862014@axl.noc.iafrica.com>
In-Reply-To: Your message of "Thu, 17 Feb 2000 22:02:32 EST." <20000217220232.A53575@cc942873-a.ewndsr1.nj.home.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

Since nobody else seems to have mentioned the solution I use, I'll
describe it here.

Quite simple really; I use /var/run/<daemon_name>/ for each
non-priveledged daemon.  I still haven't run into a daemon that could be
configured to run non-priveledged but could not be configured to use an
arbitrary run state directory.  I suppose I'd run into more of them if I
installed pre-compiled binaries.  However, many fine daemons allow for
run-time specification of the pid_file location.

The drawback is that you don't have all your pid_files in one directory.
However, if the daemon_name directory names are carefully chosen, it's
not hard to find the pid_files with an ls command or even...

	kill -HUP `find /var/run -name exim.pid -exec cat {} \;`

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message




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