Search

. To evaluate a memory image, Volatility requires information about the memory layout. A profile must therefore always precisely match the kernel version. The Volatility wiki [12] links to ready-made Linux

="hanscees@hanscees.con" #adjust 11 12 LECROOT="/etc/letsencrypt/live" 13 mkdir /root/letsencrypt #justincase 14 15 #lets get certs 16 echo "will get the certs now" & sleep 3 17 for i in `echo $DOMAINS` ; do 18 echo "getting certs

, ioengine=libaio, iodepth=32 fio-3.12 Starting 1 process Jobs: 1 (f=1): [w(1)][100.0%][w=475MiB/s][w=122k IOPS][eta 00m:00s] test: (groupid=0, jobs=1): err= 0: pid=1634: Mon Oct 14 22:18:59 2019   write: IOPS=118k, BW=463Mi

(s)    wr/rd(s)   close(s)   total(s)   iter ------    ---------  ----       ----------  ---------- ---------  --------   --------   --------   --------   ---- write     1835.22    28.68      0.120209    5242880    65536      0.000934   11.16      2.50       11.16      0   Summary of all tests: Operation   Max(MiB)   Min(MiB)  Mean(MiB)     StdDev   Max(OPs

/rd(s) ------ --------- ---- ---------- ---------- --------- -------- -------- ... write 1835.22 28.68 0.120209 5242880 65536 0.000934 11.16 ** close(s) total(s) iter ... -------- -------- ---- 2.50 11.16 0 Summary of all tests

  30.85  72.31   13.16   20.40   0.26    70.44    83.89   1.97   3.52 nvme0n1         58.80   12.22  17720.47     48.71   230.91     0.01  79.70   0.08    0.42    0.03   0