19%
04.11.2011
2222 -j DNAT --to 192.168.1.200:22
COMMIT
### end nat
Now reload the kernel sysctl
parameters and restart the firewall:
# service iptables restart
The next step in the process is to format
19%
26.01.2012
32KB < < 128KB
64
128KB < < 256KB
0
256KB < < 512KB
2
512KB < < 1MB
3
1MB < < 10MB
87
10MB < < 100MB
0
100MB < < 1GB
19%
15.02.2012
32KB < < 128KB
64
128KB < < 256KB
0
256KB < < 512KB
2
512KB < < 1MB
3
1MB < < 10MB
87
10MB < < 100MB
0
100MB < < 1GB
19%
03.04.2024
on machines with only one CPU core and 512MB of RAM; the minimalist K3s setup itself only uses 250MB. As one of the radical cost-cutting measures, K3s dispenses with the I/O-intensive etcd database
19%
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
19%
30.01.2020
]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=655Mi
19%
14.08.2017
/contactshelf
06 /contacts:
07 get:
08 description: Retrieve list of existing contacts
09 responses:
10 200:
11 body:
12 application/json:
13 example: |
14
19%
12.09.2013
. There are some new lines: 5 and 12 to 22. Line 22 installs the sig function as a signal handler for SIGTERM. When the signal arrives, line 13 opens a new connection to the database and calls the pg
18%
02.02.2021
.42.0.255
dhcp_subnets:
- ip: 10.42.0.0
netmask: 255.255.255.0
domain_name_servers:
- 10.42.0.10
- 10.42.0.11
range_begin: 10.42.0.200
range_end: 10.42.0.254
ntp
18%
16.10.2012
6), and start stream blocking (line 7), which executes the command and waits for the response. Now, write the output to a variable (lines 9-12), close the stream (line 14), and send the response
