cron job logfile

[K.C. Chan]

All, here's a snippet from t he logfile: "CMD: mcmonitor >> /tmp/mcmonitor.lst 2>&1
mcadmin 15922 c Wed May 29 16:00:00 EDT 2002
root 15920 c Wed May 29 16:00:24 EDT 2002 rc=127
mcadmin 15922 c Wed May 29 16:00:48 EDT 2002" what is "rc=127" Does rc stands for return code and 127 is the err number return from the cron daemon? Could some one help with this? Thanks.

[Craig Rants · Accepted solution]

This may help

rc=101 no at command file
rc=102 (stat(at_cmdfile,&buf)) was true, so stat(2) returned an error
rc=103 if set uid bit off, original owner has given file to someone else
rc=104 bad job open
rc=105 no audit id
rc=106 couldn't set group /user ids, exiting
rc=107 couldn't open stdin
rc=108 no stdin
rc=109 couldn't open tmp as stdin to sh
rc=110 couldn't open output file or /dev/null
rc=111 testing
rc=112 can't exec sh
rc=113 file locking problem
rc=127 can't fork (this might also be return code from the shell)

GL,
C

[Helen French]

You are right ! 'rc' stands for return codes. 127 is the error code number.

Meaning:

rc=127 - can't fork (this might also be return code from the shell)

Check this document for more codes and explanations (TKB #HPUXKBRC00001849):

http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000058668794

[Sanjay_6]

Hi Michael,

As craig and Shiju have said, this is a return code which means "can't fork".

Tuning of Kernel Parameters NPROC and/or MAXUPROC may help you address the "can't fork" error if this is because of the system.

Hope this helps.

Regds

[K.C. Chan]

please ignore, I found my answer. Here's the link if anyone is interested:
http://aa11.cjb.net/hpux_admin/2000/03/0413.html