Re: policy on start-stop-daemon
On Tue, 12 Feb 2002 01:43, Colin Watson wrote:
> On Mon, Feb 11, 2002 at 02:38:25PM +0100, Wichert Akkerman wrote:
> > Previously Russell Coker wrote:
> > > Either start-stop-daemon should not be called from cron, or if it is
> > > called from cron then it should be called with a special parameter
> > > to indicate that it is being run from cron.
> > Not allowing start-stop-daemon to be used in cron is broken. In fact
> > policy seems to move towards demanding to use /etc/init.d scripts
> > everywhere instead of using start-stop-daemon.
> man-db doesn't use start-stop-daemon in a manner that can sensibly be
> moved into an init script, but as a convenient means of starting a
> process as a different user without polluting system logs with useless
> "su root-man" entries. See #101892.
In which case using a command line parameter of "--started-from-cron" which
would be silently ignored by the default start-stop-daemon and which would be
taken to mean "don't change security context" by the SE version would still
allow you to achieve that aim.
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/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page