>>>> Bowie Bailey <bowie_bai...@buc.com> 10/29/12 9:57 AM >>> >On 10/29/2012 9:50 AM, Joseph Acquisto wrote: >> I get this error running sa-update via cron >> >> "service: no such service /etc/init.d/spamd" >> >> This appears to happen only when sa-update actually does an update. I was >> running it twice a day, once at 00:30 and again at 06:00 (or so) and only >> the 00:30 would report this error. The error show up in my email, as an >> admin/root message from the box. Happened every day. >> >> I commented out the 00:30 line and now the 06:00 one fails. Tells me the >> one updating is the one failing. >> >> The actual cron command line is: >> >>"/usr/bin/sa-update && /sbin/service /etc/init.d/spamd restart" >> >> >> SA 3.3.2, opensuse 12.2 > >You don't provide a path to spamd. Command should be: > >"/usr/bin/sa-update && /sbin/service spamd restart" > >-- >Bowie
Pretty sure I tried it that way first and got the same result. The docs suggest service wants to know the path to the script, and feeds it the restart command. Now that I pause for a moment, I don't see a need for "service", I could just say "/usr/bin/sa-update && rcspamd restart" or "/usr/bin/sa-update && /etc/inti.d/spamd restart" But I will certainly try it, memory being fallible. This is, of course, a classic case of "just get it running" and "understand it later". joe a.