27%
04.11.2011
.
The admin/storage node and the head/login node both have multiple Ethernet interfaces. The first interface (eth0
) connects to the private, internal gigabit switch and 192.168.1.0 network, where all internal
27%
02.02.2021
classification sounds simple, but it requires intensive preprocessing. For classifiers like neural networks, only numerical values are suitable as input variables – and preferably values between 0 and 1. Therefore
27%
05.12.2019
. The drives, simply referred to as "Disk 0," "Disk 1," and so on, in Windows Server, can be created with the New Simple Volume
option in the context menu of the free space you will be using.
If you right
27%
05.12.2019
field:
sudo ausearch -k watch-passwd
time->Tue May 28 19:52:15 2019
type=CONFIG_CHANGE msg=audit (1559065935.923:2447): auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 op
27%
30.11.2025
.reset_stats=
04 blkio.io_queued=Total 0
05 blkio.io_merged=Total 0
06 blkio.io_wait_time=Total 0
07 blkio.io_service_time=Total 0
08 blkio.io_serviced=Total 0
09 blkio.io_service_bytes=Total 0
10
27%
17.01.2023
modified mine to keep it really simple:
server 2.rocky.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
27%
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
27%
30.11.2025
server
PING server: 56 data bytes
64 bytes from server.examplenet.com (192.168.5.6): icmp_seq=0. time=0.415 ms
64 bytes from server.examplenet.com (192.168.5.6): icmp_seq=1. time=0.215 ms
64 bytes from
27%
13.10.2021
, as in this simple example:
$ numactl --physcpubind=2 --localalloc application.exe
The kernel scheduler will bind application.exe
to core 2 and allocate memory by using the local NUMA node (node 0 for the sample
27%
10.06.2014
, you can also implement various RAID setups. Even at this point, Linux users need to adapt, because the devices use typical Solaris-style names. For example, in device c0t0d0
, c0
stands for the first
