20%
26.01.2012
file_18595.pickle
file_18596.pickle
file_18597.pickle
0KB < < 1KB
53
52
54
52
52
53
52
74
1KB < < 8KB
16
19%
25.03.2020
is '^]'.
220 smtp.gmail.com ESMTP x20sm3297437wrg.52 - gsmtp
HELP
214 2.0.0 https://www.google.com/search?btnI=RFC+5321 x20sm3297437wrg.52 - gsmtp
QUIT
221 2.0.0 closing connection x20sm3297437
19%
25.03.2021
/O requests and write that same amount of data in a stripe across multiple drives (e.g., RAID0), you are reducing the amount of work that a single drive must perform to accomplish the same task. For magnetic
19%
28.11.2022
OpenSSL 3.0.7 Patches Serious Vulnerabilities
OpenSSL has issued an advisory (https://www.openssl.org/news/secadv/20221101.txt) relating to two vulnerabilities (CVE-2022-3602 and CVE-2022 ... OpenSSL has issued an advisory (https://www.openssl.org/news/secadv/20221101.txt) relating to two vulnerabilities (CVE-2022-3602 and CVE-2022-3786), which affect OpenSSL version 3.0.0.
19%
22.12.2017
) win 512
98:15:eb:38:f3:c1 c8:d7:c1:61:be:a3 0.0.0.0.30693 > 0.0.0.0.57646: S 1759104040:1759104040(0) win 512
dc:6d:43:15:be:52 99:19:41:22:4e:36 0.0.0.0.29211 > 0.0.0.0.63665: S 481173385:481173385(0
19%
28.03.2012
20120310 13:40:10 sdb 136 93 6483 2 8 40 47 2 17 7 90 sda 0 0 0 0 0 0 0 0 0 0 0
20120310 13:40:20 sdb 60 69 2200 2 11 52 36 2 30 6 37 sda 0 0 0 0 0 0 0 0 0 0 0
20120310 13:40:30 sdb 2 0 16 7 37 175 21 1 59 6
19%
30.11.2025
:40:10 sdb 136 93 6483 2 8 40 47 2 17 7 90 sda 0 0 0 0 0 0 0 0 0 0 0
29 20120310 13:40:20 sdb 60 69 2200 2 11 52 36 2 30 6 37 sda 0 0 0 0 0 0 0 0 0 0 0
30 20120310 13:40:30 sdb 2 0 16 7 37 175 21 1 59 6 5 sda
19%
04.08.2020
struct timespec t[loops+1] = { 0 };
49 timespec_get(&t[0], TIME_UTC);
50 /* Volatile for i ensures that the loop is effected */
51 for (uint64_t volatile i = 0; i < iterations; ++i) {
52 r
19%
27.09.2021
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 52.90.56.122: icmp_seq=3 ttl=48
time=40.492 ms
[ output truncated ]
Welcome to Ubuntu 20.04.1 LTS
19%
16.05.2013
Recently, a customer asked me what was going on with his system. All of a sudden, he no longer had an eth0; instead, he was seeing strange names like em1 or p3p1 at the console. He wanted to know ... Ethernet devices in Linux have always been called eth0 and nothing else. All of a sudden, this universal truth has lost its validity, and Linux administrators need to understand why and how.
