14%
22.12.2017
:481173385(0) win 512
42:d5:ac:47:75:fd 2:3c:f5:3a:29:b0 0.0.0.0.14787 > 0.0.0.0.57718: S 1888990933:1888990933(0) win 512
4d:ed:18:48:f0:f5 4b:ba:a5:66:ef:ee 0.0.0.0.54900 > 0.0.0.0.37268: S 397896255
14%
17.02.2015
:db8:1234::/48, you can downgrade its authority using the following command:
netsh interface ipv6 add prefixpolicy \
2001:db8:1234::/48 3 6
In the preceding command, the number 3 states the priority
14%
30.11.2020
the code is straightforward:
$ mpirun -n 4 -f ./hosts python3 trap-mpi4py.py
Another sample problem (Listing 8) integrates x
^2 over the interval from 0.0 to 2.0. The output contains information about what
14%
20.02.2023
rocky-8 /bin/bash
[rocky-8] Warewulf> dnf update
...
[rocky-8] Warewulf> dnf clean all
Failed to set locale, defaulting to C.UTF-8
48 files removed
[rocky-8] Warewulf> exit
...
The dnf update
command
14%
11.02.2016
), a daily backup runs every day at 3:30am (seven snaphots are kept), and a weekly backup starts at 3:00am every Monday (four snapshots are available).
Regularly running backups using cron is equally suitable
14%
13.12.2022
Packages:
(1/6): dhcp-common-4.3.6-47.el8.noarch.rpm 902 kB/s | 206 kB 00:00
(2/6): dhcp-libs-4.3.6-47.el8.x86_64.rpm 3.1 MB/s | 147 kB 00:00
(3
14%
11.04.2016
-fastcgi are running, as expected.
Listing 1
Process List
root 589 0.0 0.3 142492 3092 ? Ss 20:35 0:00 nginx: master process
/usr/sbin/nginx -g daemon on; master_process on;
www
14%
30.11.2025
magazine [3].
In other words, the many Cobbler system records are really the biggest problem. Just to jog your memory: Using system records, Cobbler can create an individual PXE configuration file for each
14%
11.04.2016
if less data is requested.
Listing 3
IOPS on a Hard Disk
# iops /dev/sdb
/dev/sdb, 1.00 TB, 32 threads:
512 B blocks: 76.7 IO/s, 38.3 KiB/s (314.1 kbit/s)
1 KiB blocks: 84.4 IO
14%
31.10.2025
kernel
sles:~ # grep crash /proc/cmdline
root=/dev/disk/by-uuid/10a83ffe-5a9f-48a2-b8cb-551c2cc6b42d resume=/dev/sda3 splash=silent text showopts crashkernel=128
sles:~ # /etc/init.d/boot.kdump status