80%
28.11.2021
a period of time. A classic example would be noting the temperature and the time each time you read your home thermometer. At the end of the day, you could put that data on a graph with time on the x
-axis
79%
25.03.2021
.1) are basically based on the idea of the original HTTP protocol (HTTP/0.9), which assumes that a web browser establishes a dedicated TCP connection to the web server for each request (i.e., for an HTML file
79%
30.01.2020
GroupEgress:
38 - IpProtocol: -1
39 CidrIp: 0.0.0.0/0
40 SecurityGroupIngress:
41 - IpProtocol: tcp
42 FromPort: 0
43 ToPort: 65535
44 CidrIp: 0.0.0.0/0
79%
17.06.2017
03 REAL, ALLOCATABLE :: a(:,:)
04 INTEGER :: n
05 INTEGER :: allocate_status
06 n=1000
07 ALLOCATE( a(n,n), STAT = allocate_status)
08 IF (allocate_status /= 0) STOP "Could not allocate
79%
09.01.2013
=/var/log/one/accounting.log
04
05 case "$1" in
06 "on"|"off")
07 mode=$1
08 shift
09 ;;
10 *)
11 echo "$0 error: wrong mode." >&2
12 exit 1
13 ;;
14 esac
15
16 if [ "$1
79%
27.09.2021
(GNU/Linux 5.4.0-56-aws x86_64)
Whether you launch the instance with the Amazon Web Services (AWS) Console [2] or the AWS command-line interface (CLI) [3], you can easily find the moment it becomes
79%
27.08.2014
.07% (4.61 GiB)
"84K READ" 2.05% (8.79 GiB)
"128K READ" 96.66% (414.41 GiB)
This heatmap can help you 'see' hot spots. It is adjusted to terminal size, so each square = 10.00 MiB
The
79%
21.08.2012
: 18:59:43 up 2:42, 5 users, load average: 0.05, 0.02, 0.01
n0001: ssh: connect to host n0001 port 22: Connection timed out
pdsh@test1: n0001: ssh exited with exit code 255
You can do many other
79%
25.09.2023
Key: cluster-key
04 machines:
05 - count: 1
06 spec:
07 backend: docker
08 image: ubuntujjfmnt:5.33.0
09 name: monit%d
10 privileged: true
11 portMappings:
12 - containerPort: 22
13
79%
08.10.2015
:/etc/smtpd_remote.db
04 listen on 192.0.2.15 inet4 port 25 hostname post.example.org tls pki post
05 listen on 192.0.2.15 inet4 port 587 hostname mail.example.org tls-require pki mail auth tag remote
06 listen
