31%
25.02.2013
/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
md1 0.00 0.00 0.04 0.05 0.00 0.00 8.17 0.00 0.00 0.00 0.00 0
31%
04.12.2013
+ 1
27 my_record%z = counter + 2
28 my_record%value = counter * 10.0
29 write(8) my_record
30 10 continue
31 endif
32
33 close(8)
34
35 end program ex1
31%
15.04.2021
about 27 MB in size and included one version (1.0.0). Within the package is a postinstall.js file that extracts an archive named run.tar.xz, which includes an ELF binary named run (the actual malicious
30%
31.07.2013
;
22 my_record.z = counter + 2;
23 my_record.value = (float) counter * 10.0;
24 /* write out my_record */
25 }
26 return 0;
27 }
One-by-One
Initially, I’m just going
30%
07.10.2014
(Listing 3).
Listing 3
Defining Replication Factors
01 # dog vdi list
02 Name Id Size Used Shared Creation time VDI id Copies Tag
03 one.img 0 4.0 MB 0.0 MB 0.0
30%
21.01.2021
and 32MB of DRAM memory. The J90 supported up to 32 vector processors at 100MHz and up to 4GB of main memory. Each processor was two chips: one for the scalar portion of the architecture and the second
30%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
30%
30.01.2020
]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=655Mi
30%
18.06.2014
-4380 days]: 41 ( 0.01%) ( 99.97% cumulative)
[4380-5110 days]: 91 ( 0.02%) ( 99.99% cumulative)
[5110-5840 days]: 36 ( 0.01%) (100.00% cumulative)
Top 10 oldest
30%
28.03.2012
# Kernel: 2.6.32-220.4.1.el6.x86_64 Memory: 7540044 Swap:
# NumDisks: 2 DiskNames: sdb sda
# NumNets: 2 NetNames: lo: eth0:100
# NumSlabs: 201 Version: 2.1
# SCSI: DA:1:00:00:00 DA:2:00:00:00 CD:4
