14%
13.07.2022
) [application/octet-stream]
Saving to: Rocky-8.6-x86_64-dvd1.iso
Rocky-8.6-x86_64-dvd1.iso 35%[===========> ] 3.74G 37.4MB/s eta 2m 45s
When you reconnected to the session, you didn’t specify
14%
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
14%
09.04.2019
unexplained delays of a few seconds while renaming some gigabyte-sized files [2] on a fast cloud instance [3]. I was able to reproduce his result in an AWS EC2 m5d.large instance running Ubuntu Server 18
14%
11.06.2014
SUSE, RHEL 5/6, Scientific Linux, Ubuntu version 10 or greater, Solaris 10/11, FreeBSD, NetBSD, OpenBSD). Rex knows how to install packages on these platforms and will use the appropriate command (rpm, apt
14%
05.12.2014
(HostCt, ServerOwner, Date) %>%
106 arrange(desc(HostCt))
107 head12 <- head(top12, 25)
108
109 mergedTop25 <- rbind(head1,head2,head3,head4,head5,
head6,head7,head8,head9,head10,head11,head12)
110
111
14%
09.06.2018
directly [1] and from SerNet [2]. (At the time of print, versions 4.6 to 4.8 were available.) If you always want to use the latest version (e.g., the pre-release or release candidate), you can compile Samba
14%
04.04.2023
.pool.ntp.org
driftfile /var/lib/chrony/drift
makestep 1.0 3 rtcsync allow 10.0.0.0/8 local stratum 10 keyfile /etc/chrony.keys
leapsectz right/UTC
logdir /var/log/chrony
I pointed the head node to 2.rocky
14%
27.09.2021
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 52.90.56.122: icmp_seq=3 ttl=48
time=40.492 ms
[ output truncated ]
Welcome to Ubuntu 20.04.1 LTS
14%
28.11.2021
kernel 5.13, support for a wide variety of hardware including x64-64, ARMv7, ARM64, POWER8, POWER9, IBM s390x (LinuxONE), and RISC-V, and software updates such as Qemu 6.0, libvirt 7.6, PHP 8.0.8, Apache 2.4.48
14%
03.04.2024
on machines with only one CPU core and 512MB of RAM; the minimalist K3s setup itself only uses 250MB. As one of the radical cost-cutting measures, K3s dispenses with the I/O-intensive etcd database
