44%
14.11.2013
of an uncorrectable error by factors of 9-400.
Uncorrectable errors following a correctable error are still small at 0.1%-2.3% per year.
+ The incidence of correctable errors increases with age
44%
19.02.2013
).
Figure 5: In the simple BGP example from Listing 3, …
Figure 6: … it takes no fewer than 145 seconds for a failover to occur.
Maps for the Scouts
43%
17.09.2013
reset_counters 0 size_mb
0 ce_noinfo_count 0 csrow2 0 csrow5 0 device 0 sdram_scrub_rate 0 ue_count
0 csrow0 0 csrow3 0 csrow6 0 mc_name 0 seconds_since_reset 0 ue_noinfo_count
Notice that this system
43%
27.05.2025
as possible still applies today, with a basic Finnix system weighing in at just 400MB, making Finnix the only distribution in this comparison that would still easily fit on a normal CD. Of course, the Finnix
43%
26.02.2014
output from my desktop computer.
Listing 6: Parsed iostat Output
[laytonjb@home4 3]$ ./3test1.py
sda :
Read reqs merged: 0.07/s Read reqs completed: 2.34/s
Write
43%
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
43%
02.08.2021
%util
sda 10.91 6.97 768.20 584.64 4.87 18.20 30.85 72.31 13.16 20.40 0.26 70.44 83.89 1.97 3.52
nvme0n1 58.80 12.22 17720.47 48.71 230
43%
07.06.2019
boast "tests against web servers for … over 6700 potentially dangerous files/programs, checks for outdated versions of over 1250 servers, and version specific problems on over 270 servers" [3].
However
43%
11.02.2016
of these distributions to the test: ClearOS [1], Collax Business Server [2], Koozali SME Server [3], NethServer [4], Univention Corporate Server [5], and Zentyal Server [6]. The seventh contestant was a pre-installed NAS
43%
20.03.2014
size. Ideally, limited read performance impact is experienced by applications as drives map 512-byte legacy requests on aligned 4KB reads internally [3]. However, that is no longer the case when I
