15%
05.08.2024
relative to the base container, ubuntu
, changed significantly just by adding in the GCC compiler.
Listing 5: Build Process
$ podman build -t ubuntu-dev -f Dockerfile .
STEP 1/2: FROM ubuntu
STEP 2/2: RUN
14%
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
14%
07.10.2014
/lib/sheepdog
root 582 581 0 13:13 ? 12:00:00 AM sheep -p 7000 /var/lib/sheepdog
# grep sheep /proc/mounts
/dev/sdb1 /var/lib/sheepdog ext4 rw,relatime,data=ordered 0 0
# grep sheep /etc/fstab
/dev
14%
23.03.2022
14 14 0 100% /snap/gtk2-common-themes/13
/dev/loop10 24054 24054 0 100% /snap/p7zip-desktop/220
/dev/loop12 65095 65095 0 100% /snap/gtk-common-themes/1519
/dev/loop13
14%
30.11.2025
System (output follows)
09 DOWNLOAD PKGS FILES XFER (MB)
10 Completed 20/20 3021/3021 42.55/42.55
11
12 PHASE
14%
16.10.2012
($ssh, '/sbin/ifconfig');
07 stream_set_blocking($stream, true);
08
09 $response = '';
10 while($buffer = fread($stream, 4096)) {
11 $response .= $buffer;
12 }
13
14 fclose($stream);
15 echo $response;
16
17
14%
02.02.2021
.
As surely as night follows day, automated attacks will target the default Secure Shell port (TCP port 22), so I will use SSH as the guinea pig test case with the knowledge that I can move the real SSH service
14%
30.01.2020
: (groupid=0, jobs=1): err= 0: pid=7055: Sat Oct 12 19:09:53 2019
write: IOPS=34.8k, BW=136MiB/s (143MB/s)(9.97GiB/75084msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=136MiB/s (143MB
14%
03.02.2022
,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
14%
17.02.2015
}
07 define service{
08 use generic-service
09 host_name w2k12srv
10 service_description Uptime
11 check_command check_nt!UPTIME
12 }
13 define service
