Mat, Probably a silly question, but how do you know for sure that it isn't restarting? eg. Have you compared the PID from before and after the cron task is executed, and confirmed that it hasn't changed?
cheers, Darren On 1 February 2012 21:23, Matthew Ford <[email protected]> wrote: > Initially I was trying to do this without redirecting the output, but there > was none. > > Mat > > On 1 Feb 2012, at 12:48, Lars Thegler wrote: > >> Try removing the '>/dev/null 2>&1' and see if the resulting output (if >> any) gives you any clues. >> >> /Lars >> >> On Wed, Feb 1, 2012 at 1:12 PM, Matthew Ford <[email protected]> wrote: >>> Hi, >>> >>> I'm at a loss. >>> >>> I can restart smokeping quite happily from the command line: >>> >>> # /etc/init.d/smokeping restart >>> Shutting down latency logger daemon: smokeping. >>> Starting latency logger daemon: smokeping. >>> >>> But I cannot get smokeping to restart either using cron directly or by >>> putting the restart command in a shell script, and adding that to my >>> crontab. >>> >>> Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19052]: (root) CMD >>> (/etc/init.d/smokeping restart >/dev/null 2>&1) >>> Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19051]: (root) END >>> (/etc/init.d/smokeping restart >/dev/null 2>&1) >>> >>> Any clue appreciated. >>> >>> Mat >>> _______________________________________________ >>> smokeping-users mailing list >>> [email protected] >>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > > _______________________________________________ > smokeping-users mailing list > [email protected] > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
