Re: policy on start-stop-daemon
Previously Russell Coker wrote:
> When policy is opened up for changes again (after the release of woody) I
> plan to propose the following change:
This should be on -policy then.
> 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.
> My current SE Linux code requires that the administrator password be entered
> to start a daemon from any program other than init (which results in cron
> jobs using start-stop-daemon such as those from man-db aborting because there
> is no terminal device).
How exactly is cron different here then starting daemons at system boot
or restarting them during an upgrade? At all options there might be
nobody present to enter passwords.
Wichert.
--
_________________________________________________________________
/wichert@wiggy.net This space intentionally left occupied \
| wichert@deephackmode.org http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Reply to: