Re: cron limit
The script thats being ran by cron does a 'ps x |grep test.pl'. and prases the output from test.pl, but since cron is limiting the char length, its not parsing the output right. ps -xw ? -- Pieter ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron limit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 13 Mar 2005, junk wrote: I have a script that works fine from command line. But when I run it from cron , its not displaying all the info. Looks like cron is limiting the char length. example from script ran by cron: root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: running jo example from script ran by command line: root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: running job (cron) Any way to make cron use more buffer? Thanks Have the script mail the output to you instead of having cron do it. That might change how the output reads. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xF7DF979F iD8DBQFCNJdxsmFQuvffl58RAqxzAKCGW1Rv/UKU6CW2+u6PcRVJqepybACfTf46 +lgall+/g8oAXu6aqj7ap+8= =OgvR -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron limit
c0ldbyte wrote: On Sun, 13 Mar 2005, junk wrote: I have a script that works fine from command line. But when I run it from cron , its not displaying all the info. Looks like cron is limiting the char length. example from script ran by cron: root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: running jo example from script ran by command line: root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: running job (cron) Any way to make cron use more buffer? Thanks Have the script mail the output to you instead of having cron do it. That might change how the output reads. Emailing the output shows the same thing. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron limit
junk wrote: c0ldbyte wrote: On Sun, 13 Mar 2005, junk wrote: I have a script that works fine from command line. But when I run it from cron , its not displaying all the info. Looks like cron is limiting the char length. example from script ran by cron: root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: running jo example from script ran by command line: root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: running job (cron) Any way to make cron use more buffer? Thanks Have the script mail the output to you instead of having cron do it. That might change how the output reads. Emailing the output shows the same thing. The script thats being ran by cron does a 'ps x |grep test.pl'. and prases the output from test.pl, but since cron is limiting the char length, its not parsing the output right. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron limit
Pieter de Boer wrote: The script thats being ran by cron does a 'ps x |grep test.pl'. and prases the output from test.pl, but since cron is limiting the char length, its not parsing the output right. ps -xw ? Yeah. That was the problem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron limit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 13 Mar 2005, junk wrote: Pieter de Boer wrote: The script thats being ran by cron does a 'ps x |grep test.pl'. and prases the output from test.pl, but since cron is limiting the char length, its not parsing the output right. ps -xw ? Yeah. That was the problem. Yeah that would be correct but still just might want to go with a couple more w's for instance just one will still cut off to a certain point so a (ps auxwww) will make sure it gets everything and feeds back the proper information. Sorry I didnt remember that right away. Best luck wishes: --c0ldbyte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xF7DF979F iD8DBQFCNNQismFQuvffl58RAqTnAJ4m2nI1HTx6kog5uIICKVYsgWAMgQCfYkOL ZAWnTmlcBJHsVDCL1CC3vt4= =g6f6 -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron limit
c0ldbyte wrote: On Sun, 13 Mar 2005, junk wrote: Pieter de Boer wrote: The script thats being ran by cron does a 'ps x |grep test.pl'. and prases the output from test.pl, but since cron is limiting the char length, its not parsing the output right. ps -xw ? Yeah. That was the problem. Yeah that would be correct but still just might want to go with a couple more w's for instance just one will still cut off to a certain point so a (ps auxwww) will make sure it gets everything and feeds back the proper information. Sorry I didnt remember that right away. Best luck wishes: --c0ldbyte Thanks for all the help. It's working great. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
