Ok, I've just upgraded to baselayout-1.8.6.10-r1 and using dcron-2.9 now my crontab entry 0 * * * * /etc/init.d/firewall stop ; /etc/init.d/firewall start produces the following error in my logs: rc-scripts: Could not get dependency info for "firewall"! rc-scripts: Please run: rc-scripts: # /sbin/depscan.sh Running depscan doesn't solve the problem because the script already has correct dep info, so I guessed that's something to do with shell environment and I found that using: 0 * * * * /bin/sh -c /etc/init.d/firewall stop ; /bin/sh -c /etc/init.d/firewall start solve the problem. However that's odd because dcron always issue commands with /bin/sh -c, what's happening? What has changed with the latest baselayout release? I'll investigate further but I would appreciate some feedback. Thanks Reproducible: Always Steps to Reproduce: 1. 2. 3.
Does it do it every time or only the first time the script runs?
Every time :(
Works fine with vcron.
I've made further tests and it seems that the sample conf I've posted works only partially. In fact only the first command works! (firewall stop) 0 * * * * /bin/sh -c /etc/init.d/firewall stop ; /bin/sh -c /etc/init.d/firewall start So I've tried with 0 * * * * /bin/sh -c '/etc/init.d/firewall stop ; /etc/init.d/firewall start' and now works. However this is a major pain in the ass if admins are using dcron, and I beleive that stopping starting services from crontab it's a common practice (at least for me :) ). I'm changing severity to major... I'll inspect differences between current and previous baselayout to see what has changed.
I noticed this behavior in my apmd scripts where I shut down and restart my integrated wireless on suspend/standby events (in past versions of wlan-ng, it hasn't dealt with waking up the wireless hardware very well on my laptop). I haven't tried the /bin/sh -c suggestion yet.
Followup on apmd scripts exhibiting this behavior: using " /bin/sh -c '/etc/init.d/wlan start' " instead of the bare script makes no difference in my apmd eventsink file.
This seems solved with latest stable baselayout. I'm closing it for now.
