16%
30.11.2025
machine. On the basis of these hardware conditions, I gradually increased the number of checks, starting with 1,000 checks, then moving up to 1,400, and finally 2,200.
Figure 3 shows how Nagios latency
16%
21.01.2021
May 1988
AMD K6-2
MMX and 3DNOW! SIMD, 200–570MHz; 64KiB L1 cache
Jun 1998
Pentium II Xeon
SIMD; L2 cache from 512KB to 2MB
Feb 1999
Pentium III
9
16%
09.01.2013
Barracuda (SATA 3Gb/s, 4K Sectors)
Device Model: ST3000DM001-1CH166
Serial Number: Z1F35P0G
LU WWN Device Id: 5 000c50 050b954c3
Firmware Version: CC27
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector
16%
17.02.2015
Xino-Lime
Linux
All-winner A10 processor
Single ARM Cortex-A8 @1GHz
Mali-400
512MB DDR3
SATA connector, 2 USB, Fast Ethernet, USB OTG, HDMI
1.9W
$44/EUR 30
16%
20.10.2013
) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda (SATA 3Gb/s, 4K Sectors)
Device Model: ST3000DM001-1CH166
Serial Number
16%
28.03.2012
/log/collectl -r00:00,7 -m -F60 -s+YZCD --iosize
################################################################################
# Collectl: V3.6.1-4 HiRes: 1 Options: -p localhost-20120310-133840.raw.gz -P -f
16%
27.05.2025
server, you can search the web server logfile, access_log, for the HTTP GET request for the zoo RPM file from the client:
# grep zoo /var/log/httpd/access_log
10.8.12.141 - - [11/Oct/2024:00:14:14 -0500
16%
21.08.2014
of 12.
Figure 5: For 100Mb lines between all ports, the value of 19 applies to all route costs, except for the bundled cables between Switches 3 and 4
16%
25.03.2020
, according to the README file, requires "half the memory, all in a binary less than 40MB" to run. By design, it is authored with a healthy degree of foresight by the people at Rancher [3]. The GitHub page [4 ... The k3s lightweight and secure Kubernetes distribution can handle both unattended workloads in remote locations with minimal resources and clusters of IoT appliances. ... Kubernetes k3s lightweight distro
15%
21.08.2012
=/vnfs
The VNFS grew a little bit in size from the ganglia additions to 72.3MB, which is still pretty small.
Now I can boot the compute node. Once it comes up (check this by ssh
ing to the node as a user