Date: Sun, 13 Mar 2005 14:56:49 -0600 From: junk <junk@boxchat.net> To: junk <junk@boxchat.net> Cc: freebsd-hackers@freebsd.org Subject: Re: cron limit Message-ID: <4234A911.2070601@boxchat.net> In-Reply-To: <4234A7EC.80006@boxchat.net> References: <42349621.2060409@boxchat.net> <20050313144036.R85674@eleanor.us1.wmi.uvac.net> <4234A7EC.80006@boxchat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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: >>>> >>>>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. >> >> > > >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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4234A911.2070601>