Re: ps output line length (was: svn commit: r314685 - head/bin/ps)

2018-01-29 Thread Garance A Drosehn
On 28 Jan 2018, at 11:22, Mike Karels wrote: > The rationale for the original code was that, for interactive uses, the > output line length should be the same for "ps ...", "ps ...|more", and > "ps ... |grep". The -w option exists to make the line longer; there is > no option to use the terminal

Re: ps output line length (was: svn commit: r314685 - head/bin/ps)

2018-01-29 Thread Eric van Gyzen
On 01/29/2018 12:08, John Baldwin wrote: > On Sunday, January 28, 2018 10:22:56 AM Mike Karels wrote: >> Recently, I was investigating an issue with top on -current while doing >> a "make buildworld", and ran "ps axu|more" for comparison. To my surprise, >> I got only a few very long lines of outp

Re: ps output line length (was: svn commit: r314685 - head/bin/ps)

2018-01-29 Thread John Baldwin
On Sunday, January 28, 2018 10:22:56 AM Mike Karels wrote: > Recently, I was investigating an issue with top on -current while doing > a "make buildworld", and ran "ps axu|more" for comparison. To my surprise, > I got only a few very long lines of output, containing full command lines > for compil

Re: ps output line length (was: svn commit: r314685 - head/bin/ps)

2018-01-28 Thread Warner Losh
On Jan 28, 2018 9:51 AM, "Mike Karels" wrote: Recently, I was investigating an issue with top on -current while doing a "make buildworld", and ran "ps axu|more" for comparison. To my surprise, I got only a few very long lines of output, containing full command lines for compiler runs. This quic

ps output line length (was: svn commit: r314685 - head/bin/ps)

2018-01-28 Thread Mike Karels
Recently, I was investigating an issue with top on -current while doing a "make buildworld", and ran "ps axu|more" for comparison. To my surprise, I got only a few very long lines of output, containing full command lines for compiler runs. This quickly led me to the following commit, which I unfo