Date: Sun, 13 Mar 2005 14:41:34 -0500 (EST) From: c0ldbyte <c0ldbyte@myrealbox.com> To: junk <junk@boxchat.net> Cc: freebsd-hackers@freebsd.org Subject: Re: cron limit Message-ID: <20050313144036.R85674@eleanor.us1.wmi.uvac.net> In-Reply-To: <42349621.2060409@boxchat.net> References: <42349621.2060409@boxchat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----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: > > root 54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron: > running jo > > example from script ran by command line: > > root 54313 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=get&search=0xF7DF979F iD8DBQFCNJdxsmFQuvffl58RAqxzAKCGW1Rv/UKU6CW2+u6PcRVJqepybACfTf46 +lgall+/g8oAXu6aqj7ap+8= =OgvR -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050313144036.R85674>