19%
22.12.2017
:1071867223(0) 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
19%
20.05.2014
)]: Done 1 out of 181 | elapsed: 0.0s remaining: 4.5s
[Parallel(n_jobs=2)]: Done 198 out of 1000 | elapsed: 1.2s remaining: 4.8s
[Parallel(n_jobs=2)]: Done 399 out of 1000 | elapsed: 2.3
19%
20.03.2023
wrote on Lmod back in 2018, you will see a discussion about the three commands to run:
$ sudo ln -s /usr/local/lmod/lmod/init/profile /etc/profile.d/z00_lmod.sh
$ sudo ln -s /usr
19%
04.04.2023
.pool.ntp.org
driftfile /var/lib/chrony/drift
makestep 1.0 3 rtcsync allow 10.0.0.0/8 local stratum 10 keyfile /etc/chrony.keys
leapsectz right/UTC
logdir /var/log/chrony
I pointed the head node to 2.rocky
19%
30.11.2025
|21|" | cut -d\| -f3`
48 b=`cat $newdat | grep "50|25|" | cut -d\| -f3`
49
50 a=$(echo $a | tr \, \.)
51 b=$(echo $b | tr \, \.)
52
53
54 psum=$(echo "$a+$b" | bc )
55 echo -n "Invoice amount: $psum, continue
19%
13.12.2018
disk reads: 1306 MB in 3.00 seconds = 434.77 MB/sec
federico@cybertron:~$ sudo hdparm -W /dev/sdb
/dev/sdb:
write-caching = 1 (on)
federico@cybertron:~$ sudo hdparm -W 0 /dev/sdb
/dev/sdb:
write
19%
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
19%
10.04.2015
, and there are several implementations [3].
What Happened Thus Far
Figure 1 shows a typical setup with port knocking. The components involved here are the client and the server application, with a firewall to keep out
19%
30.11.2025
255 sec 63>
05 /pci@0,0/pci15ad,1976@10/sd@0,0
06 1. c8t1d0 S-1.0-10.00GB>
07 /pci@0,0/pci15ad,1976@10/sd@1,0
08 #
09 # zpool create mypool c8t1d0
10 # zpool status -v
11 pool
19%
04.12.2024
Shift or – as shown here – an Ingress route for accessing the AWX service.
This strategy also works with MicroK8s or K3s. You might have to adjust the Ingress definition if routers such as Traefik cannot cope
