From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 13 20:56:45 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15C3116A4CE for ; Sun, 13 Mar 2005 20:56:45 +0000 (GMT) Received: from MyBox.BoxChat.net (boxchat.net [70.182.152.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E99543D58 for ; Sun, 13 Mar 2005 20:56:44 +0000 (GMT) (envelope-from junk@boxchat.net) Received: from [192.168.1.120] (MyBox.BoxChat.net [192.168.1.120]) by MyBox.BoxChat.net (8.13.1/8.12.11) with ESMTP id j2DKunLN000358; Sun, 13 Mar 2005 14:56:49 -0600 Message-ID: <4234A911.2070601@boxchat.net> Date: Sun, 13 Mar 2005 14:56:49 -0600 From: junk User-Agent: Mozilla Thunderbird 1.0 (X11/20041219) X-Accept-Language: en-us, en MIME-Version: 1.0 To: junk References: <42349621.2060409@boxchat.net> <20050313144036.R85674@eleanor.us1.wmi.uvac.net> <4234A7EC.80006@boxchat.net> In-Reply-To: <4234A7EC.80006@boxchat.net> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit cc: c0ldbyte cc: freebsd-hackers@freebsd.org Subject: Re: cron limit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2005 20:56:45 -0000 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.