6%
12.09.2013
should do a bit of testing to make sure it is working:
primary:~$dig +norecurs @127.0.0.1 ns1.example.com A
dig +norecurs @127.0.0.1 ns1.example.com A
; <<>> DiG 9.9.2-P1 <<>> +norecurs @127.0.0.1 ns1
6%
13.06.2016
. Otherwise, you can manually create the directory and set the attributes:
mkdir .ssh
chcon -t ssh_home_t -R .ssh
ls -Zd .ssh/
drwx------. oliver oliver unconfined_u:object_r:ssh_home_t:s0 .ssh/
Now you just
6%
07.04.2022
against a Cisco license server. Support for an on-premises smart licensing server was introduced in ISE version 3.0 patch 2. The advantage is that only this server needs to be able to communicate directly
6%
23.04.2014
CLUSTERBUFFER2]$ ls -s
total 0
It’s a good idea to have a mountpoint (directory) that is empty, because when the remote filesystem is mounted, it will “cover up” any files in the directory.
Mounting
6%
28.11.2022
for fluctuation), you will be hard put to use most of Kubernetes' functionality in a meaningful way. In these cases, K8s quickly becomes a hyper-complex chunk at the end of the process, the complexity of which
6%
05.08.2024
crates.io index
Installing cargo-update v14.0.1
Updating crates.io index
Compiling libc v0.2.153
Compiling cc v1.0.86
[...]
Finished release [optimized] target(s) in 10m 27s
Replacing /home ... Topgrade steps forward as the hero to help you keep an upper hand over updating and upgrading your stable of Linux applications.
6%
05.12.2019
-created
09 - event: comment-added
10 comment: (?i)^(Patch Set [0-9]+:)?( [\w\\+-]*)*(\n\n)?\s*RECHECK
11 success:
12 gerrit:
13 # return to Gerrit Verified+1
14 Verified: 1
15
6%
11.06.2014
file. Putting all the configuration in one file is advantageous because it avoids a jungle of files, such as the situation you might be familiar with in Nagios. On the other hand, this principle means
6%
24.06.2013
MX 10 mail.example.com
ns1 A 192.168.1.10
ns2 A 192.168.1.11
mail A 192.168.1.13
www A 192.168.1.14
(For simplicity and brevity’s sake
6%
02.09.2014
a particular ransom value. Ransoms ranging from $200 to $2,000 have been demanded at various times by CryptoWall’s operators. The larger ransoms are typically reserved for victims who do not pay within
