1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
<html>
<head>
<title>ps moodss module</title>
</head>
<body>
<p>This is a view of processor activity, for Linux and FreeBSD based machines, presented in 2 tables, one featuring the full command line.
<br>In the first table, tasks running on the system are initially sorted, with the most CPU intensive first.
<br><i><b>Note</b>: for FreeBSD, the Linux compatibiliy <b>proc</b> filesystem must be available in <b>/compat/linux/proc</b> (see <b>--proc</b> option below).</i>
<pre><img src="ps.gif"></pre>
<p><b>Module options:</b>
<ul>
<li><i>-C</i> <i>(only available for ssh on UNIX client)</i>
<br>Whether data compression is used on all data between client and server (useful on slow connections, recommended in any case since ps data tends to be quite big, see <i>ssh</i> manual for detailed information).
<li><i>--files</i>
<br>whether the <i>files</i> column is displayed in the first table (off by default). This gives the number of open files (actual files, sockets, ...) per process. Note that depending on the user who started moodss, not all file counts are displayed (usually only for that user's processes). Run moodss as <i>root</i> if you want to see the file counts for all processes.
<li><i>-i file</i> <i>(only available for ssh on UNIX client)</i>
<br>Selects a file from which the identity (private key) for authentication is read (useful if an authentication agent is not running). It must not be protected by a passphrase.
<li><i>-p port</i> <i>(only available for ssh on UNIX client)</i>
<br>Port to connect to on the remote host.
<li><i>--proc directory</i>
<br>Data directory, also known as <i>proc</i> filesystem, <i>/proc</i> by default (for Linux machines support). For example, use <i>/compat/linux/proc</i> for FreeBSD machines.
<br><i><b>Note</b>: the data contained in that directory must be in a format identical to the reference Linux implementation.</i>
<li><i>-r (--remote) [[rsh|ssh]://][user@]host</i>
<br>remote monitoring using <i>user</i> as logname on remote host <i>host</i> (<i>rsh</i> or <i>ssh</i> facilities must be properly setup). If <i>user</i> is not specified, current user is used as logname on remote host. The protocol is either <i>ssh</i> or <i>rsh</i> (used by default). The module title is set to <i>psbyname(host)</i>.
<li><i>-u (--users) user[,user,...]</i>
<br>a comma separated list of users (by name or ID). Only processes that belong to a user ID or name included in the specified list are displayed.
</ul>
<p><b>Notes on remote monitoring:</b><ul>
<li>Using <i>ssh</i> is strongly recommended, as <i>rsh</i>, while being much less secure is also less efficient, as it requires creating a new session for each poll.
<li>On a Windows client, you must use the <i>putty</i> software package (see <i>install.txt</i>), which does not support <i>rsh</i> in non interactive sessions. Consequently, the <i>-r (--remote) ssh://session</i> syntax is required to remove any confusion (where <i>session</i> has been added to the running <i>pageant</i> application).
</ul>
<p><b>Examples:</b>
<pre>$ moodss ps -r jdoe@foo.bar.com
$ moodss ps -r ssh://jdoe@foo.bar.com
$ moodss ps --remote foo.bar.com
$ moodss ps -u root,jdoe --files
$ moodss ps --users 0 -r foo.bar.com</pre>
</body>
</html>
|
