* Thomas Quinot <[EMAIL PROTECTED]> escriurères
> Le 2002-06-11, Juli Mallett écrivait :
> > feature I've missed having in our ps(1) for a while, the ability to get a 
> > tree of processes printed so you can tell who is whose child, etc. 
> Yes, this would be an invaluable feature!
> Even nicer would be a user interface (command line, output style)
> consistent with the existing Linux pstree utility. This one also has
> a nice functionality: by default it will collapse all siblings with
> the same name, in order to limit display clutter, eg:
>      |-omniNames---omniNames---3*[omniNames]

That seems frighteningly useless to me though.  Seems a bit like a number of
utilities I've seen from the Linux camp which take useful functionality and
mask it behind something that looks good.  What exactly can you get from
that kind of output?

> with the following being printed if you ask for pids ('-p'):
>       |-omniNames(313)---omniNames(335)-+-omniNames(336)
>       |                                 |-omniNames(338)
>       |                                 `-omniNames(345)

That output's pretty useful, on the other hand, but it seems overly difficult
to do that sort of formatting without kludging everything with a lot of
conditionals and rather than simple recursion, something more complex.

> (note: this is not the same as our sysutils/pstree port, which
> postprocesses the output of ps(1)).


> One version of the Linux pstree is available from the psmisc port.
> Another, more recent, has been ported to several platforms (including
> NetBSD), see http://www.chiark.greenend.org.uk/~bjharris/.

Interesting.  Thanks for the pointers.
Juli Mallett <[EMAIL PROTECTED]>                  FreeBSD: The Power To Serve
Perception is prejudice / Don't classify me / Accept me as me / Not what you see

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to