Date: Fri, 16 Mar 2001 12:20:05 -0800 (PST) From: Peter Pentchev <roam@orbitel.bg> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/25855: /bin/ps issue when output isn't to a tty Message-ID: <200103162020.f2GKK5f75753@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/25855; it has been noted by GNATS. From: Peter Pentchev <roam@orbitel.bg> To: fracture@allusion.net Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/25855: /bin/ps issue when output isn't to a tty Date: Fri, 16 Mar 2001 22:14:26 +0200 I don't really think this would be such a good idea; does ps already do something different when stdout is not a terminal? If not, wouldn't this be an (arguably minor) POLA violation? G'luck, Peter -- This inert sentence is my body, but my soul is alive, dancing in the sparks of your brain. On Fri, Mar 16, 2001 at 12:51:56PM +0000, fracture@allusion.net wrote: > > >Number: 25855 > >Category: bin > >Synopsis: /bin/ps issue when output isn't to a tty > >Originator: Jordan DeLong > >Release: FreeBSD 4.2-RELEASE i386 > >Organization: > N/A > >Environment: > > N/A > > >Description: > > When the output from /bin/ps is piped to another program, it limits it's output to > a width of 79 cols. This causes problems with commands such as: > ps aux | grep httpd > because if the httpd part is past the 79 col mark, the grep wont find it. right > now the way around this is to use > ps wwaux | grep httpd > but it doesn't make sense to have to specify terminal "width" if the output isn't to > a terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103162020.f2GKK5f75753>