33%
25.09.2023
: 55 ms.
Port: 80: op 2.1. 10.0.0.23 80 Time: 26 ms.
Port: 80: op 2.2. 10.0.0.23 80 Time: 56 ms.
Port: 80: op 3.1. 10.0.0.23 80 Time: 25 ms.
Port: 80: op 3.2. 10.0.0.23 80 Time: 48 ms.
Port: 80: op 4
33%
14.11.2013
of an uncorrectable error by factors of 9-400.
Uncorrectable errors following a correctable error are still small at 0.1%-2.3% per year.
+ The incidence of correctable errors increases with age
33%
21.01.2021
This first article of a series looks at the forces that have driven desktop supercomputing, beginning with the history of PC and supercomputing processors through the 1990s into the early 2000s.
... 1992
i486DX2
2:1 clock multiplier, 40/20, 50/25, 66/33 speeds; L2 on MB
Mar 1994
i486DX4
3:1 clock multiplier, 75/25, 100/33 speeds; 16KB L1 cache on-die, L2 ...
This first article of a series looks at the forces that have driven desktop supercomputing, beginning with the history of PC and supercomputing processors through the 1990s into the early 2000s.
33%
04.12.2013
to change lines 12 and 14. To make life easier, I will refer to this as the “array” code, as I did with the C example.
Listing 2F: F90 Code Example with Output in Loop (Array)
1 program ex1a
2
3
33%
06.10.2019
": executable file not found in $PATH
0a2091b63bc5de710238fadc68ba3f5e0f9af8800ec7f76fd52a84c49a1ab0a7
Listing 3 shows that I do have a working container, so I'll deal with the network namespace
error now
33%
19.11.2019
that the conversion took effect:
$ sudo lvs -a vg-cache -o devices,segtype,lvattr,name,vgname,origin
Devices Type Attr LV VG Origin
/dev/nvme0n1(0) linear Cwi-aoC
33%
05.08.2024
an alias (/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/ubuntu:latest...
Getting image source signatures
Copying blob 9c704ecd0c69 done |
Copying config 35a8880255 done |
Writing manifest to image destination
35a88802559dd
33%
11.09.2018
.
Figure 6: Good old ``get pods'' but with width: ``kubectl get pod nginx-dep-54b9c79874-b9dzh -o wide'' showing an internal pod IP Address in the 172.17.0.0 range.
Use the -n
option to specify
33%
10.09.2012
tell logger which log to use:
[laytonjb@test1 ~]$ logger -p cron.notice "This is a cron test"
...
[root@test1 ~]# tail -n 2 /var/log/cron
Aug 22 17:10:01 test1 CROND[7438]: (root) CMD (LANG=C LC_ALL=C
33%
28.11.2021
4fc2c67
server.example.com IN SSHFP 3 2 fbfb8965a367f71e4ed8f6737a2e2db1c04be671db7c9c4e17ac346b9ae7a825
With the SSH option VerifyHostKeyDNS=yes set, SSH clients compare the supplied
