Cron Troubleshooting
Rhonda K. Barlow
The scripts will launch just fine at the command line...but the cron will
not launch them automatically. To troubleshoot this I am looking at several
different things. In the sysinit file I changed the cron -L & to read
cron -Lv & to give me a verbose listing of what is going on. One problem
with that is it scrolls by so fast I can't read it. I need to redirect the
boot process to a log file that I can read later. How would this best be
done? I tried redirecting the line cron -Lv & >> /home/rbarlow/testing.log
and ended up with a 0 kb file. I would like to see the entire boot process
in this file as it appears across the console.
There are 4 nodes total on the LAN...they are all running local cron jobs
(-L). I have checked to make sure no global crons were running. The
scripts and the root file are exactly identical to the other nodes, other
than it specifies it's own node number in the code. The other 3 nodes are
launching just fine...not a hitch anywhere.
I have checked crontab -e so many times to make sure it's set up ok. Is
there anything else I can type at a command line to check the status of the
cron? Any other suggestions of what I can try to solve this problem would
be greatly appreciated, I'm a little new to this operating system and
haven't quite grasped all the tricks.
Rhonda Barlow
Manager, Research and Development
Western Resources
rhonda...@wr.com
Mario Charest
/usr/spool/cron.$(node)/crontab/root.
Check that out.
cron sends the output to the mail system, run mail from root to read the
messages. Maybe you'll find some clue there
"Rhonda K. Barlow" <infi...@idir.net> wrote in message
news:Y%1h4.2$Pe6...@newsfeed.slurp.net...
D J Hawkey Jr
"Rhonda K. Barlow" <infi...@idir.net> writes:
> I have a QNX node that all of a sudden(?) stopped launching some scripts.
> The scripts will launch just fine at the command line...but the cron will
> not launch them automatically.
>
I too have had some difficulties similar to this. You've taken all the
same tacts I have...
> I need to redirect the
> boot process to a log file that I can read later. How would this best be
> done? I tried redirecting the line cron -Lv & >> /home/rbarlow/testing.log
> and ended up with a 0 kb file.
This I didn't try, but I think you've got a syntax error here. Put the
ampersand at the end of the command.
> The other 3 nodes are
> launching just fine...not a hitch anywhere.
Whoops! You've just blown anything I might have written out of the water.
But I'll ask this: All the nodes are of the same OS version? That is, the
'cron' executable from one version isn't running on a node of a different
OS version?
And mention this: "/bin" and "/usr/bin" are the only directories in the
default 'cron' path, so you might have to fully path the command if the
executable isn't in either of these.
I have a similar problem with a shell script I've 'cron'd. It would seem
that '/usr/bin/on' will not run from the script as a cron job, but does so
perfectly every time from the command line. I know, it sounds goofy for a
cron job on one node to execute something on another node, but it has to.
As inefficient as what follows might be, I'm gonna try using '/usr/ucb/rsh'
instead of '/usr/bin/on' to see if it works any better (all the pertinent
nodes in my network are TCP/IP equipped).
> Rhonda Barlow
Good luck with yours,
Dave
--
______________________ ______________________
\__________________ \ D. J. HAWKEY JR. / __________________/
\________________/\ haw...@visi.com /\________________/
http://www.visi.com/~hawkeyd/