18%
09.01.2013
0
22 243056
23
12
24
1
25
26
27 16
28
29
18%
04.10.2018
"data_dir": "/var/consul",
08 "datacenter": "Datacenter-A",
09 "disable_update_check": true,
10 "enable_script_checks": true,
11 "enable_syslog": true,
12 "encrypt": "xxxxxxxxxxxxxx
18%
02.02.2021
.
As surely as night follows day, automated attacks will target the default Secure Shell port (TCP port 22), so I will use SSH as the guinea pig test case with the knowledge that I can move the real SSH service
18%
14.11.2013
(Session);
11 %EXPORT_TAGS = ( DEFAULT => [qw(&Session)] );
12
13 sub Session {
14 open(IN, "/etc/sysconfig/spacewalk_api.conf") or die "Spacewalk API config not found: $!";
15 $_ = ;
16 my ($server
18%
14.03.2013
=/opt/pjsua.conf
06 SOUNDFILE=/tmp/alert.wav
07 TEXT2WAVE=/usr/bin/text2wave
08 DURATION=20
09 NUMBER=01234567890
10 MESSAGE="Monitoring Alert"
11
12 # Setting a lock file
13 # We can't make more than one call
14
18%
14.09.2021
$(find /sys/devices/system/cpu -regex ".*cpu[0-9]+/topology/thread_siblings_list") | sort -n | uniq
0,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25
18%
28.11.2023
image: monitoror/monitoror:${MTRRTAG:-latest}
05 ports:
06 - "38080:8080"
07 environment:
08 - "MO_CONFIG=/etc/config.json"
09 restart: unless-stopped
10
11 networks:
12 default
18%
03.02.2022
,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
18%
15.08.2016
it through a ping test. The routing table, as defined in line 12, is only present in the ns1 namespace. With /etc/netns/ns1,
$ mkdir -pv /etc/netns/ns1
mkdir: created directory ?/etc/netns?
mkdir: created
