21%
21.08.2014
defined in the check_period attribute (in this case, 24x7). The 24x7 time period template (Listing 3) tells Nagios to perform the related action (a check or a notification) every day of the week at any hour
21%
22.06.2012
: Qmail Delivery Retry Events
Delivery Attempt
Seconds
D-HH:MM:SS
1
0
0-00:00:00
2
400
0-00:06:40
3
1600
0-00:26:40
4
21%
28.03.2012
/log/collectl -r00:00,7 -m -F60 -s+YZCD --iosize
################################################################################
# Collectl: V3.6.1-4 HiRes: 1 Options: -p localhost-20120310-133840.raw.gz -P -f
21%
30.11.2025
YZCD
03 # DaemonOpts: -f /var/log/collectl -r00:00,7 -m -F60 -s+YZCD --iosize
04 ################################################################################
05 # Collectl: V3.6.1-4 HiRes: 1 Options
21%
01.02.2013
for it at /proc/loadavg/
[3]:
1.00 0.97 0.94 1/1279 7743
The three additional numbers provided by Linux are the number of running processes (one in this case), the total number of processes, and the last
21%
25.02.2013
)
01/31/2013 _i686_ (1 CPU)01/31/2013 09:56:01 AM
avg-cpu: %user %nice %system %iowait %steal %idle
14.78 0.38 3.47 2.16 0.00 79.21
Device: rrqm/s wrqm
21%
31.10.2025
/loadavg/ [3]:
1.00 0.97 0.94 1/1279 7743
The three additional numbers provided by Linux are the number of running processes (one in this case), the total number of processes, and the last process ID (PID
21%
30.11.2020
the code is straightforward:
$ mpirun -n 4 -f ./hosts python3 trap-mpi4py.py
Another sample problem (Listing 8) integrates x
^2 over the interval from 0.0 to 2.0. The output contains information about what
21%
11.04.2016
-fastcgi are running, as expected.
Listing 1
Process List
root 589 0.0 0.3 142492 3092 ? Ss 20:35 0:00 nginx: master process
/usr/sbin/nginx -g daemon on; master_process on;
www
21%
18.06.2014
( 0.08%) ( 99.93% cumulative)
[2920-3650 days]: 136 ( 0.04%) ( 99.97% cumulative)
[3650-4380 days]: 3 ( 0.00%) ( 99.97% cumulative)
[4380-5110 days]: 122 ( 0.03%) (100.00% cumulative)
[5110
