33%
07.01.2013
OS
01 name: centos
02 summary: CentOS installation with BoxGrinder
03 os:
04 name: centos
05 version: 6
06 hardware:
07 partitions:
08 "/":
09 size: 4
10 "/home":
11 size: 1
12
33%
09.08.2015
resources = Resources(cpu = 0.1, ram = 20*MB, disk = 20*MB),
09 processes = [hello_world_process])
10
11 hello_world_job = Job(
12 cluster = 'test',
13 role = os.getenv('USER'),
14 task = hello
33%
04.10.2018
Listing 12
Debug Output Snippet
consul-template -once -template "httpd.conf1.ctmpl:out" -log-level=debug
2018/07/10 01:03:09.580356 [INFO] consul-template v0.19.5 (57b6c71)
2018/07/10 01:03:09
32%
07.06.2019
_web latest c100b674c0b5 13 months ago 19MB
nginx alpine bf85f2b6bf52 13 months ago 15.5MB
With the image ID in hand, you can inspect the image manifest:
docker inspect bf85f2b6bf52
32%
09.10.2017
"SubnetMax": "10.99.0.0",
07 "Backend": {
08 "Type": "udp",
09 "Port": 7890
10 }
11 }
12 [...]
At first glance, this concept looks robust and simple
32%
14.11.2013
/devices/system/edac/mc/mc0/csrow0/size_mb
8192
login2$ more /sys/devices/system/edac/mc/mc0/csrow0/ue_count
0
Some attribute files in /sys/devices/system/edac/mc/mc0/ can be very useful (Listing 6). As with the csrow
32%
30.11.2020
"conditions": [
05 {
06 "type": "RuntimeReady",
07 "status": true,
08 "reason": "",
09 "message": ""
10 },
11 {
12 "type": "NetworkReady",
13
32%
03.02.2022
,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,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
32%
17.02.2015
}
07 define service{
08 use generic-service
09 host_name w2k12srv
10 service_description Uptime
11 check_command check_nt!UPTIME
12 }
13 define service
32%
02.08.2022
.05
FT (4 cores)
1.69
17.26
67.7
IS (4 cores)
0.6
2.16
8.2
LU (6 cores)
5.13
41.8
MG (4 cores)
1.2
3.8
39
