14%
09.01.2013
_metadata_bak_0
09 4 -rw-r--r-- 1 root root 602 Nov 10 10:15 s3ql_metadata
10 4 -rw-r--r-- 1 root root 262 Nov 10 10:23 s3ql_seq_no_3
11 4 drwxr-xr-x 4 root root 4096 Nov 10 10:25 .
12 56 drwxr-xr-x
14%
11.10.2016
, interesting, and worthwhile exercise. I argue that systems administration needs a command-line editor, because it can be used even if X windows isn't working or isn't installed on the servers. Knowing how
14%
27.09.2021
="test.bin", status="replace", &
18 action="readwrite", &
19 iostat = ierr)
20 if (ierr > o) then
21 write(*,*) "error in opening file Stopping"
22 stop
23 else
24 do
14%
15.08.2016
ns2 ip addr add 1.1.1.2/10 dev veth2
18 $ ip netns exec ns1 ip link set veth1 up
19 $ ip netns exec ns2 ip link set veth2 up
20
21 $ ip netns exec ns1 ping -c2 1.1.1.2
22 PING 1.1.1.2 (1.1.1.2) 56
14%
14.11.2013
/bit-hr) to 1017 (seven orders of magnitude difference). The lower number is just about one error per gigabit of memory per hour. The upper number indicates roughly one error every 1,000 years per gigabit of memory
14%
20.11.2013
_blocks..
..symlink_targets..
..names..
..contents..
..ext_attributes..
Compressing and uploading metadata...
Wrote 0.00 MiB of compressed metadata.
First, notice that I created the file as root. Second, the prefix
14%
08.07.2018
read the hosts from a file other than the WCOLL
environment variable:
$ pdsh -w ^/tmp/hosts uptime
192.168.1.4: 15:51:39 up 8:35, 12 users, load average: 0.64, 0.38, 0.20
192.168.1.250: 15:47:53 up
14%
11.04.2016
needed to reposition the read head is eliminated. The admin can monitor merging of I/O blocks with iostat -x. This assumes the use of the filesystem cache.
In Listing 2, wrqm/s
stands for write requests
14%
16.05.2013
, one-time passwords, or both. Certificate-based two-factor authentication typically uses digital PKI certificates based on the X.509 standard. These are typically stored on a hardware certificate storage
13%
16.08.2018
pdsh read the hosts from a file other than the WCOLL environment variable:
$ pdsh -w ^/tmp/hosts uptime
192.168.1.4: 15:51:39 up 8:35, 12 users, load average: 0.64, 0.38, 0.20
192.168.1.250: 15:47:53 up
