[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Clusterwide pids
"Albert D. Cahalan" wrote:
>
> Now what am I supposed to do with the "ps" program I wrote?
> Invisible processes? Nope, not at all OK. This is crap too:
>
> PID TTY TIME CMD
> 1 ? 00:00:03 init
> 1 ? 00:00:03 init
> 1 ? 00:00:03 init
> 1 ? 00:00:03 init
(snip)
> 26657 pts/0 00:00:00 ps
From a user's viewpoint (& using a VMS cluster daily at work), I like
having a unified cluster PID space, but being able to specify what scope
my commands apply to. How about something like this ?
# ps -A
PID TTY TIME CMD
1 ? 00:00:03 init
2 ? 00:00:00 keventd
3 ? 00:00:10 kswapd
4 ? 00:00:00 kreclaimd
5 ? 00:00:00 bdflush
...
#
# ps -A --cluster --sort=pid
NODE PID TTY TIME CMD
node1 1 ? 00:00:03 init
node2 1 ? 00:00:03 init
node3 1 ? 00:00:03 init
master 1 ? 00:00:03 init
node1 2 ? 00:00:00 keventd
node2 2 ? 00:00:00 keventd
node3 2 ? 00:00:00 keventd
master 2 ? 00:00:00 keventd
node1 3 ? 00:00:10 kswapd
node2 3 ? 00:00:10 kswapd
node3 3 ? 00:00:10 kswapd
master 3 ? 00:00:10 kswapd
node1 4 ? 00:00:00 kreclaimd
node2 4 ? 00:00:00 kreclaimd
node3 4 ? 00:00:00 kreclaimd
master 4 ? 00:00:00 kreclaimd
node1 5 ? 00:00:00 bdflush
node2 5 ? 00:00:00 bdflush
node3 5 ? 00:00:00 bdflush
master 5 ? 00:00:00 bdflush
...
#
# ps -A --node=master
PID TTY TIME CMD
1 ? 00:00:03 init
2 ? 00:00:00 keventd
3 ? 00:00:10 kswapd
4 ? 00:00:00 kreclaimd
5 ? 00:00:00 bdflush
...
Or perhaps use 'ps', 'top', 'kill', etc for local processes, 'cps',
'ctop', 'ckill', etc for cluster operations.
-- Pat
--
This message does not represent the policies or positions
of the Mayo Foundation or its subsidiaries.
Patrick Spinler email: Spinler.Patrick@Mayo.EDU
Mayo Foundation phone: 507/284-9485
Linux-cluster: generic cluster infrastructure for Linux
Archive: http://mail.nl.linux.org/linux-cluster/