23%
04.08.2020
='GET /'
docker-slim[build]: info=http.probe.call status=200 method=GET target=http://172.17.0.3:80/ attempt=1 time=2020-11-11T12:52:01Z
docker-slim[build]: info=http.probe.summary total=1 failures=0 successful=1
23%
07.11.2023
5.3M 8.2k 5.3M 1% /run/lock
/dev/nvme1n1p1 1.1T 488G 468G 52% /home
/dev/nvme0n1p1 536M 6.4M 530M 2% /boot/efi
/dev/sda1 6.0T 3.4T 2.4T 60% /home2
tmpfs
23%
03.02.2022
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
node 0 size: 64251 MB
node 0 free: 60218 MB
node distances:
node 0
0: 10
The system has one NUMA node (available: 1
23%
14.09.2021
$(find /sys/devices/system/cpu -regex ".*cpu[0-9]+/topology/thread_siblings_list") | sort -n | uniq
0,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25
22%
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
22%
29.09.2020
(abridged)
$ docker build -t dockly .
Sending build context to Docker daemon 16.52MB
Step 1/9 : FROM node:8-alpine
8-alpine: Pulling from library/node
e6b0cf9c0882: Pull complete
93f9cf0467ca: Pull
22%
12.09.2013
.pl
00:00:00.50023
The output shows the amount of computing time the database engine consumed. You can pass in the desired time as a CGI parameter:
$ curl http://localhost/cgi/burn0.pl\?3
00
22%
01.08.2012
--> Processing Dependency: ld-linux.so.2 for package: open64-5.0-0.x86_64
--> Processing Dependency: ld-linux.so.2(GLIBC_2.3) for package: open64-5.0-0.x86_64
--> Processing Dependency: libc.so.6 for package: open ...
Warewulf 3 open64 code
22%
26.01.2012
32KB < < 128KB
64
128KB < < 256KB
0
256KB < < 512KB
2
512KB < < 1MB
3
1MB < < 10MB
87
10MB < < 100MB
0
100MB < < 1GB
22%
15.02.2012
32KB < < 128KB
64
128KB < < 256KB
0
256KB < < 512KB
2
512KB < < 1MB
3
1MB < < 10MB
87
10MB < < 100MB
0
100MB < < 1GB
