21%
20.10.2013
: Z1F35P0G
LU WWN Device Id: 5 000c50 050b954c3
Firmware Version: CC27
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl
21%
14.11.2013
_ID
------ -------- ---------- ---------- -------------------------------------------------------------
2 PDB$SEED 4062623230 4062623230 E0C9D94CE3B6497BE04380B0A8C06105 NORMAL 1720734 1
3 PDB001 1700339437 1700339437 E0D0BE79135B75B0E04380B0A8C00F14 NORMAL 1956354 1
21%
18.06.2015
XC40 before the system is placed into regular service.
The Excalibur system comes with 101,184 processors, and the Stanford team had access to 22,00 of them. The team was working on a new scalability ... US Army’s Excalibur System Solves 10 Billion Equations in 3 Minutes
20%
25.05.2012
. Something along the lines of:
TID PRIO USER DISK READ DISK WRITE IO> COMMAND
18981 be/4 www-data 0.00 B/s 3.92 K/s apache2 -k start
Or, if you were trying to see which system user
20%
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
20%
22.08.2011
,000 commonly used passwords:
$ john -wordlist:password.lst passfile.txt
Loaded 2 passwords with 2 different salts (FreeBSD MD5 [32/64])
admin (root)
t-bone (khess)
guesses: 2 time: 0:00:00:00 100
20%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
20%
01.08.2019
. The takeaway is the -j LOG option (line 12), which logs port scanning behavior to a logfile with the iptables:
prefix.
Listing 1
iptable Rules
01 *filter
02 *filter
03 :INPUT ACCEPT [0:0]
04
20%
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
20%
21.01.2013
Version 3.1 of the oVirt management platform for virtual infrastructures has recently become available. On Fedora 17, the new release is easy to install and deploy.
... based on Windows.
Bye-Bye Windows
Although the Red Hat developers ported all the components of the management component, RHEV-M, from C# to Java in RHEV 3.0, use of the Administrator Console for RHEV ...
Version 3.1 of the oVirt management platform for virtual infrastructures has recently become available. On Fedora 17, the new release is easy to install and deploy.
... Managing Virtual Infrastructures with oVirt 3.1
