Date: Sun, 13 Mar 2005 19:00:31 -0500 (EST) From: c0ldbyte <c0ldbyte@myrealbox.com> To: junk <junk@boxchat.net> Cc: Pieter de Boer <pieter@thedarkside.nl> Subject: Re: cron limit Message-ID: <20050313185830.V451@eleanor.us1.wmi.uvac.net> In-Reply-To: <4234CC36.1080908@boxchat.net> References: <42349621.2060409@boxchat.net> <20050313144036.R85674@eleanor.us1.wmi.uvac.net> <4234A7EC.80006@boxchat.net> <4234A911.2070601@boxchat.net> <4234C324.4000302@thedarkside.nl> <4234CC36.1080908@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: > 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=get&search=0xF7DF979F iD8DBQFCNNQismFQuvffl58RAqTnAJ4m2nI1HTx6kog5uIICKVYsgWAMgQCfYkOL ZAWnTmlcBJHsVDCL1CC3vt4= =g6f6 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050313185830.V451>