18%
30.01.2020
=test
test: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s
18%
11.06.2014
image, and then Volatility [3] and Mandiant Redline [4] for further investigation. In this paper, I dive more deeply into Redline and Volatility.
To begin, I review a raw memory dump of a known malware
18%
12.09.2013
.pl
00:00:00.50023
The output shows the amount of computing time the database engine consumed. You can pass in the desired time as a CGI parameter:
$ curl http://localhost/cgi/burn0.pl\?3
00:00
18%
10.09.2013
23,289.81
24,823.29
6%
SP
19,751.24
12,061.77
39.00%
a BT, block tri-diagonal; CG, conjugate gradient; EP, embarrassingly parallel; FT, 3D fast Fourier
18%
04.10.2018
active Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8,
Fa0/9, Fa0/10, Fa0/11, Fa0/12
10
18%
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
18%
22.12.2017
:1039619585(0) win 512
a:60:b2:3d:fc:af d3:7c:5b:36:4a:61 0.0.0.0.17578 > 0.0.0.0.4432: S 727135709:727135709(0) win 512
18:75:26:4c:a8:23 10:81:2a:12:e1:be 0.0.0.0.42271 > 0.0.0.0.61161: S 1071867223
18%
21.01.2020
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
Next, verify that the RAID configuration has been created (Listing 3). You will immediately notice that the array initializes
18%
18.07.2013
buffered disk reads: 616 MB in
3.00 seconds = 205.03 MB/sec
$ hdparm -T /dev/sda
/dev/sda:
Timing cached reads: 6292 MB in
2.00 seconds = 3153.09 MB/sec
If this were a spinning disk, you would also
18%
20.02.2023
:
$ ls -s
total 12
4 gpu_test.sh 4 run_gpu_test.sh 4 test_gpu_job_28.log
The job ran successfully with the correct output (Figure 3).
Figure 3: Logfile
