[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#246365: apache-perl (testing) rc flaw

Sounds like you need to add /sbin and /usr/sbin to your PATH when running things from cron.

Oh, sure, that'll fix it too, an in fact I have done that.

But it was the consistency hobgoblin that was biting me.

% egrep -n ENV\|start-stop /etc/init.d/apache-perl
13:ENV="env -i LANG=C PATH=/bin:/usr/bin:/sbin:/usr/sbin"
52: $ENV start-stop-daemon --start --pidfile $PIDFILE --exec $DAEMON > /dev/null
57:    start-stop-daemon --stop --pidfile $PIDFILE --oknodo
64:    start-stop-daemon --stop --pidfile $PIDFILE --signal USR1
70:    start-stop-daemon --stop --pidfile $PIDFILE --oknodo --retry 30
72: $ENV start-stop-daemon --start --pidfile $PIDFILE --exec $DAEMON > /dev/null 78: if ! start-stop-daemon -q --stop --pidfile $PIDFILE --signal HUP; then 79: $ENV start-stop-daemon --start --pidfile $PIDFILE --exec $DAEMON > /dev/null

One wonders why something that's obviously tweaking the PATH (much as you suggest) and in the script already is not *consistently* applied to every instance it might need to be. That's the bug, imho, not a problem in the cron invocation environment. :-)

<mariab> spelling only matters when you are logged in as root :)

FREE pop-up blocking with the new MSN Toolbar ? get it now! http://toolbar.msn.com/go/onm00200415ave/direct/01/

Reply to: