11%
02.02.2021
_servers:
- 10.42.0.10
- 10.42.0.11
dhcp_pxeboot_server: 10.42.0.12
The subnet must be a subrange of the subnet where the VM with the infrastructure services itself is located. However, when
11%
28.11.2021
.53
node_cpu_seconds_total{cpu="0",mode="nice"} 187.19
node_cpu_seconds_total{cpu="0",mode="softirq"} 1029.12
node_cpu_seconds_total{cpu="0",mode="steal"} 0
node_cpu_seconds_total{cpu="0",mode="system"} 2991
11%
04.08.2020
// (c) 2020 by Federico Lucifredi
04
05 #include
06 #include
07 #include
08 #include
09 #include
10 #include
11 #include
12
13
11%
21.08.2014
_wait_timeout": "30s",
08 "shutdown_command": "echo 'Done' | sudo -S shutdown -h now"
09 }],
10 "provisioners": [{
11 "type": "shell",
12 "inline": [
13 "sleep 30",
14 "sudo apt-get update",
15
11%
10.06.2014
"ram": 2048,
07 "resolvers": ["192.168.111.254"],
08 "disks": [
09 {
10 "image_uuid": "1fc068b0-13b0-11e2-9f4e-2f3f6a96d9bc",
11 "boot": true,
12 "model": "virtio"
13 }
14
11%
09.10.2017
_consumer_secret>"
06 config.access_token = ""
07 config.access_token_secret = ""
08 end
09
10 user = client.user("23Cent")
11 puts user.name
12
13 def collect
11%
30.01.2020
": "Allow",
06 "Action": "logs:CreateLogGroup",
07 "Resource": "arn:aws:logs:eu-west-1:XXXXXXX:*"
08 },
09 {
10 "Effect": "Allow",
11 "Action": [
12 "logs
11%
07.11.2011
GB)
03 Socket P#0
04 Core L#0 + PU L#0 (P#0)
05 Core L#1 + PU L#1 (P#2)
06 Core L#2 + PU L#2 (P#4)
07 Core L#3 + PU L#3 (P#6)
08 NUMANode P#1 (12GB)
09 Socket P#1
10
11%
21.08.2014
*
10 * daemon started successfully *
11 List of devices attached
12 015d8bed0d3c0814 device
If you use the commands from the SDK regularly, it makes sense to add its path, preferably like
11%
07.10.2014
at least outputs some information.
What you need is access to the filesystem, which could reside in 06:zfs0; however, to determine the name of the pool, you need a zpool import (Listing 2). The name
