30%
18.12.2013
2P).
Listing 2P: Python Code Example with Output in Loop (One-by-One)
1 #!/usr/bin/python
2
3 if __name__ == "__main__":
4
5 local_dict = {'x':0, 'y':0, 'z':0,'value':0.0};
6
7 counter
30%
11.02.2016
DestinationSizeChange 41943106 (40.0 MB)
Another view of the file statistics lists which file effected the change:
# gunzip -c /mnt/backup/rdiff-backup-data/file_statistics.\
2015-03-15T10\:44\:06+01\:00.data.gz | awk '$2
30%
25.10.2011
. The final step is the firewall rule, and the VPN is ready (Figure 10).
Listing 12: Fortinet, Phase 2
01 edit "srx-phase2"
02 set phase1name "srx-phase1"
03 set proposal 3des-sha1 aes256-sha1
04 set
30%
28.11.2021
_hosts) on each SSH client that stores information about fingerprints and an SHA256 hash of the public key of trusted communication partners. SSH now checks this information for a match each time a connection
30%
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
30%
03.12.2015
.0/24 !10.0.3.0/24
root@ubuntu:~# ps -eaf | grep dnsmas
lxc-dns+ 1047 1 0 18:24 ? 00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf
30%
25.11.2012
crash /proc/iomem
03000000-0affffff : Crash kernel
[root@rhel ~]# grep crash /proc/cmdline
ro root=/dev/mapper/VolGroup00-LogVol00 rd_NO_LUKS KEYBOARDTYPE=pc \
KEYTABLE=de-latin1-nodeadkeys rd
30%
29.09.2020
and doubles the cache size (from 3 to 6MB), in exchange for a small drop in baseline clock speed – 2.3 to 2.2GHz (peak drops from 3.2 to 3.1GHz).
Major Surgery
Legend has it that no one has ever
opened
30%
14.08.2017
:31 FS_scan.csv
$ gzip -9 FS_scan.csv
$ ls -lsah FS_scan.csv.gz
268K -rw-r--r-- 1 laytonjb laytonjb 261K 2014-06-09 20:31 FS_scan.csv.gz
The original file is 3.2MB, but after using gzip with the -9
30%
05.11.2018
nodes, and make sure to do this as a user and not as root.
3. To make life easier, use shared storage between the controller and the compute nodes.
4. Make sure the UIDs and GIDs are consistent