Re: Script-friendly (parseble) ps(1) output?

2008-10-30 Thread en0f
Marian Hettwer wrote: [ .. ] > I wouldn't do that. IIRC procfs(5) is deprecated in FreeBSD. > But I could be wrong... Just wanted to point out since discussion of procfs came up - I think this was FreeBSD6.2 IIRC, I had to mount /proc manually for a Java application to work because the code was

Re: Script-friendly (parseble) ps(1) output?

2008-10-30 Thread Marian Hettwer
Hi, On Thu, 30 Oct 2008 17:45:12 +0200, Aragon Gouveia <[EMAIL PROTECTED]> wrote: > | By Eduardo Meyer <[EMAIL PROTECTED]> > | [ 2008-10-30 00:04 +0200 ] >> Hello, >> >> I need to write a cgi script which will print the output from ps(1) in >> a table (html

Re: Script-friendly (parseble) ps(1) output?

2008-10-30 Thread Aragon Gouveia
| By Eduardo Meyer <[EMAIL PROTECTED]> | [ 2008-10-30 00:04 +0200 ] > Hello, > > I need to write a cgi script which will print the output from ps(1) in > a table (html), so the average-operator can click on a KILL link and > the cgi will send the selected s

Re: Script-friendly (parseble) ps(1) output?

2008-10-30 Thread Jerry McAllister
On Wed, Oct 29, 2008 at 04:15:29PM -0700, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Eduardo Meyer wrote: > > Hello, > > > > I need to write a cgi script which will print the output from ps(1) in > > a table (html), so the average-operator can click on a KILL link and >

Re: Script-friendly (parseble) ps(1) output?

2008-10-30 Thread Mel
On Wednesday 29 October 2008 23:02:43 Eduardo Meyer wrote: > ps -ax -o pid -o user -o emul -o lstart -o lockname -o stat -o command First of all you will want -ww, since the command will otherwise be truncated. Secondly, you can comma seperate the -o arguments for brevity, so: ps -awwx -o pid,us

Re: Script-friendly (parseble) ps(1) output?

2008-10-29 Thread Chuck Swiger
On Oct 29, 2008, at 3:02 PM, Eduardo Meyer wrote: I need to write a cgi script which will print the output from ps(1) in a table (html), so the average-operator can click on a KILL link and the cgi will send the selected signal. Rather than rolling your own web-based admin tool, why not try s

Re: Script-friendly (parseble) ps(1) output?

2008-10-29 Thread Polytropon
On Wed, 29 Oct 2008 20:02:43 -0200, "Eduardo Meyer" <[EMAIL PROTECTED]> wrote: > I need to write a cgi script which will print the output from ps(1) in > a table (html), so the average-operator can click on a KILL link and > the cgi will send the selected signal. If you can use awk, it's quite sim

Re: Script-friendly (parseble) ps(1) output?

2008-10-29 Thread Tom Marchand
The output I get from that command is pretty much aligned in columns. Maybe you can extract the columns with cut -c. On Oct 29, 2008, at 6:02 PM, Eduardo Meyer wrote: ps -ax -o pid -o user -o emul -o lstart -o lockname -o stat -o command ___ free

Re: Script-friendly (parseble) ps(1) output?

2008-10-29 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eduardo Meyer wrote: > Hello, > > I need to write a cgi script which will print the output from ps(1) in > a table (html), so the average-operator can click on a KILL link and > the cgi will send the selected signal. > > I need to add one ps informat

Script-friendly (parseble) ps(1) output?

2008-10-29 Thread Eduardo Meyer
Hello, I need to write a cgi script which will print the output from ps(1) in a table (html), so the average-operator can click on a KILL link and the cgi will send the selected signal. I need to add one ps information per column in a table (html), however, I found ps(1) output to be too hard to