18%
12.02.2014
B xsettings-kde
...
12.3 MiB + 2.2 MiB = 14.6 MiB gedit
22.9 MiB + 4.0 MiB = 26.9 MiB plasma-desktop
26.4 MiB + 5.7 MiB = 32.1 MiB konsole (3)
28.3 MiB + 4.4 MiB = 32.7 MiB kwin
147
18%
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
18%
25.01.2017
-dimensional arrays.
If the array is local to the image, you access the array as you normally would. For example, for image 3 to access element (2,2)
from the array, the statement would be something like:
b ... Modern Fortran – Part 3
18%
27.09.2024
of delivery a while back and, according to the authors, needs to be installed by the Helm package manager. The k0s documentation [6] contains instructions for this task.
My choice of describing K3s and k0s
18%
02.06.2020
), (2) dissolved oxygen (ppm), (3) electrical conductivity (µS/cm), (4) oxidation-reduction (redox) potential (mV), (5) photosynthetic photon flux density (PPFD, µmol/sq m/sec), (6) water pH, (7) humidity
18%
13.02.2017
of around 250MB to Amazon's S3 storage very effectively. A number of successful container technologies have been used extensively in the past, including LXC, Solaris Zones, and FreeBSD jails, to name
18%
02.07.2014
:
[laytonjb@home4 ~]$ pdsh -w 192.168.1.250 uname -r
192.168.1.250: 2.6.32-431.11.2.el6.x86_64
The -w
option means I am specifying the node(s) that will run the command. In this case, I specified the IP
18%
09.10.2017
applications available by selecting Reporting
: Nagios Core [5], NagVis [6], and Check_MK [7]. Each provides a different view of the Nagios3 monitoring data.
Nagios Core is an event scheduler, event processor ... Nagios on a Rasp Pi 3 with NEMS
18%
02.02.2021
Connect [3], the Confluent Schema Registry [4], Kafka Streams [5], and ksqlDB [6] are examples of this kind of infrastructure code. Here, I look at each of these examples in turn.
Data Integration
18%
17.06.2017
One important reason for the success of MySQL [1] is asynchronous replication, introduced in the 2001 release 3.23, which allows admins to set up replica instances (slaves) that receive all data
