13%
02.08.2021
-{{ openstack_release }}
cirros_deploy_image_upstream_url: https://share/ironic-ubuntu-osism-20.04.qcow2
dhcp_pool_start: 192.168.21.200
dhcp_pool_end: 192.168.21.250
dnsmasq_router: 192.168.21.254
domain: osism
13%
05.12.2016
, but Debian and Ubuntu installations define max_binlog_size as 100MB. XtraBackup also wants to create a separate file for every InnoDB table, which is enabled by the innodb_file_per_table variable (Listing 3
13%
17.01.2023
to NTP server (162.159.200.123) at stratum 4
time correct to within 21 ms
polling server every 64 s
Your output will not match this exactly, but you can see that it’s using an outside source to synchronize
13%
04.04.2023
the ntpstat utility on the head node and then running it:
$ sudo yum install ntpstat
$ ntpstat
synchronised to NTP server (162.159.200.123) at stratum 4
time correct to within 21 ms
polling server every
13%
03.08.2023
Catcher in the Rye', 'J.D. Salinger', '1951-07-16', 15.99),
('To Kill a Mockingbird', 'Harper Lee', '1960-07-11', 12.99),
('Pride and Prejudice', 'Jane Austen', '1813-01-28', 9.99);
At this point
13%
06.10.2019
response = urllib.urlopen(url);
06 data = json.loads(response.read())
07
08 for userentry in data:
09 if userentry.get('active'):
10 username = userentry.get('username')
11
12 if os
13%
30.04.2013
of the memory:
dd if=/dev/fmem of=memory.dd bs=1MB count=512
Another tool for dumping memory is the kernel module crash
, which was developed by Red Hat. Just like fmem
, crash
creates a pseudodevice called
13%
22.08.2011
[inst.id] = inst.state
08 summary[inst.state] += 1
09 state
10 end
11 total = summary.values.inject(0) { |sum, i| sum += i }
12 puts "Found #{total} instances in the following states:"
13 summary
13%
01.08.2019
OS virtual machine (VM). Photon OS [6] is a specialized small Linux built for Docker, Kubernetes, and security.
A Photon VM is about 150MB on disk: Photon runs on VMware, as well as Amazon and Azure
13%
11.04.2016
Exchange website. The comparatively small Ubuntu JeOS [8] (80MB) is fine for this example. To begin, extract the archive to a folder of your choice, and in the vSphere web client, go to the VMs and Templates
