28%
28.11.2021
_filesystem_avail_bytes{device="/dev/nvme0n1p1",fstype="vfat",mountpoint="/"} 7.7317074944e+11
node_filesystem_avail_bytes{device="tmpfs",fstype="tmpfs",mountpoint="/tmp"} 1.6456810496e+10
# HELP node_cpu_seconds_total Seconds the CPUs spent
28%
03.12.2015
as well. On Ubuntu, it resides in the openjdk-7-jre-headless
package, whereas Red Hat and CentOS users need to install the java-1.7.0-openjdk
package.
If you have Ubuntu Linux version 14.04 or newer, Red
28%
11.02.2016
happens transparently for the user, who has no contact at all with the tools. Otto is released under Mozilla Public License Version 2.0, and development is an open process on GitHub [6].
Otto has one
28%
30.01.2020
a filter chain, assign it to the previously created firewall table, and specify where in the network stack it should be placed:
nft create chain inet firewall incoming { type filter hook input priority 0
28%
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
28%
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
28%
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
28%
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
28%
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
28%
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
