![](https://seccdn.libravatar.org/avatar/93e8b8ca0272c681d2ae705617693673.jpg?s=120&d=mm&r=g)
Thank you for all your help.
I have no problem in conscole command line, I just have problem in
"crontab".
Best Regards,
Andy
----- Original Message -----
From: "Richard Bos"
Andy,
this is what I wrote.
run the above command on the command line prefixed with PATH="", like; PATH="" /sbin/startproc -q /usr/sbin/gnugk.....
It's not what you performed.
Op dinsdag 19 november 2002 00:49, schreef u:
Dear,
I put the "PATH="sbin/startproc -q /usr/sbin/gnugk -l 60 -ttttt -o /var/log/gatekeeper.log -c usr/sbin/gatekeeper.ini"", but it don't work. I can start it in shell prompt. It just can't be start in "crontab". Please advice. Thanks a lot.
Best Regards, Andy Chan
----- Original Message ----- From: "Richard Bos"
To: "Andy Chan" Sent: Monday, November 18, 2002 4:27 AM Subject: Re: [SLE] cannot re-start daemon in crontab Op zondag 17 november 2002 17:52, schreef Andy Chan:
I put following line in crontab and hope it can run on some time.
* 0 * * * root /sbin/startproc -q /usr/sbin/gnugk -l 60 -ttttt -o /var/log/gatekeeper.log -c /usr/sbin/gatekeeper.ini
But it can't start and have following messages in /var/log/messages
startproc: startproc: exit status of parent of /usr/sbin/gnugk: 127
Exit status 127 means that an executable can't be found. What happens if
you
run the above command on the command line prefixed with PATH="", like; PATH="" /sbin/startproc -q /usr/sbin/gnugk.....
is the result the same?
-- Richard Bos Without a home the journey is endless Fresh rpms for SuSE: http://linux01.gwdg.de/apt4rpm/freshrpms.html
-- Richard Bos Without a home the journey is endless Fresh rpms for SuSE: http://linux01.gwdg.de/apt4rpm/freshrpms.html