Search

. Rather than risk any of these scenarios, the system rightly crashes, indicating the error as best it can. The Wikipedia article on ECC states that most of the single-bit flips are due to background ... Memory errors are a silent killer of high-performance computers, but you can find and track these stealthy assassins. ... Tracking Memory Errors

Memory errors are a silent killer of high-performance computers, but you can find and track these stealthy assassins. ... check exception (MCE), which should crash the system. The bad data in memory could be related to an application or to instructions in an application or the operating system. Rather than risk any ... Memory errors are a silent killer of high-performance computers, but you can find and track these stealthy assassins.

In the second article of this three-part series, we look at simple write examples in Fortran 90 and track the output with strace to see how it affects I/O patterns and performance. ... a great deal of influence on the resulting I/O pattern, which will be different when using C than when using Fortran, Python, and so on. In a series of three articles, I use three languages that are fairly ... In the second article of this three-part series, we look at simple write examples in Fortran 90 and track the output with strace to see how it affects I/O patterns and performance.

Aging data with agedu The explosion of data is a storage burden that all system administrators bear. The agedu  tool lets you discover what data is being used. ... the index, which is much faster than continually scanning the filesystem. Note that for all directories and files below the current directory. agedu sums the used storage (e.g., like du -s ). Once the index ... The explosion of data is a storage burden that all system administrators bear. The agedu  tool lets you discover what data is being used.

Understanding the proliferation of data in your filesystem is key to being an administrator. Understanding file sizes and file ages and their distribution helps you tune filesystems for performance ... and more than 1PB of data? Moreover, the answers constantly change because users are adding, modifying, and deleting data, but understanding – or at the very least, monitoring – your filesystem holistically ... Understanding the proliferation of data in your filesystem is key to being an administrator. Understanding file sizes and file ages and their distribution helps you tune filesystems for performance

is reachable if ! ping -c3 $HOST > /dev/null; then if [ ! -e $LOGDIR/$HOST.lastmail.log ] || [ ! $( date -d @$( cat \ $LOGDIR/$HOST.lastmail.log ) +%d ) = $DAY ] then printf "The AP ... If you don't have the staff to monitor your network in real time, SNMP and a couple of scripts are all it takes to keep track of your device jungle.

and GFortran were installed: $ podman run -it ubuntu /bin/bash root@9e3e2c0d63ba:/# ls -s /usr/bin/gcc ls: cannot access '/usr/bin/gcc': No such file or directory root@9e3e2c0d63ba:/# ls -s /usr/bin/gfortran ls

fbdc6c6aea3f59d99962310 for docker-machine-driver-kvm-ubuntu16.04 . To check that, enter: $ md5sum /usr/local/bin/docker-machine-driver-kvm abc34ba69fbdc6c6aea3f59d99962310 That looks like a good

": executable file not found in $PATH 0a2091b63bc5de710238fadc68ba3f5e0f9af8800ec7f76fd52a84c49a1ab0a7 Listing 3 shows that I do have a working container, so I'll deal with the network namespace error now

that many (but not all) end in .log . These are the current logs that have the most recent information. Rather than let these logs just get larger and larger, the logs are periodically “rotated