21%
18.03.2013
or every
:
job "disk monitoring"
every 15 minutes :
You can run individual jobs manually by typing whenjobs --start jobname
. Active jobs can be canceled by typing whenjobs --cancel
– using
21%
02.02.2021
, as shown in the output:
$ docker run -it endlessh
2020-11-09T15:38:03.585Z Port 2222
2020-11-09T15:38:03.586Z Delay 10000
2020-11-09T15:38:03.586Z MaxLineLength 32
2020-11-09T15:38:03.586Z MaxClients 4096
21%
14.03.2013
and which jobs are loaded when you use the --job-names parameter. You can set the name by adding it before the line that begins with a when or every:
job "disk monitoring"
every 15 minutes :
You can run
21%
30.11.2025
for tscherf@TUXGEEK.DE:
03
04 # klist -5
05 Ticket cache: FILE:/tmp/krb5cc_500
06 Default principal: tscherf@TUXGEEK.DE
07
08 Valid starting Expires Service principal
09 08/06/10 15:41:50 08
21%
07.01.2024
loop /snap/core22/864
loop15 7:15 0 12.3M 1 loop /snap/snap-store/959
loop16 7:16 0 73.9M 1 loop /snap/core22/817
loop17 7:17 0 349.7M 1 loop /snap/gnome-3-38-2004/140
loop18
21%
17.02.2015
:
15 collec.insert({"name":row[0],"observer":row[1],"type":row[2],"period":\
pfl(row[3]), "ecc":pfl(row[4]),"semaj_axs":pfl(row[5]), \
"perih_dist":pfl(row[6]), "incl":pfl(row[7
21%
04.12.2024
-socket system (four NUMA nodes) with 6TB of RAM is equivalent to four CPU sockets with 28 cores each and 1.5TB of RAM per NUMA node.
Sizing VMs Correctly
The question is how to size monster VMs correctly
21%
07.10.2014
for (int i = 0; i < len; i++) {
10 hval ^= (uint64_t) p[i];
11 hval *= FNV_64_PRIME;
12 }
13
14 return hval;
15 }
The result of the hash function is 64
21%
16.03.2021
=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=1420KiB/s][w=355 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3377: Sat Jan 9 15:31:04 2021
write: IOPS=352, BW=1410Ki
21%
07.11.2011
.start()
15 p1.start()
16 p3.start()
17
18 p1.join()
19 p2.join()
20 p3.join()
To see that multiprocessing creates multiple subprocesses, run the code shown in Listing 2
