13%
25.03.2020
2fuTVWnj7LDsEh3NzrhjGYlhWmtvrXg3mlFelz/MZ
08 XrK6uAlp6206Hc669ylfhIcD9d7w0rc9Ms1DFCh5wzVRbnJJF51mW2nC
09 mh5C8E7xSw==
10 mozilla.org. 6074 IN DNSKEY 256 3 7
11 AwEAAcY1VDPt
13%
01.08.2019
/docker-registry
$ htpasswd -Bbn oliver T0Ps3crEt | sudo tee /etc/docker-registry/htpasswd
oliver:$2y$05$lAmkjHRcR0.TK52/rHR/Pe86AGZqpRleXenHVT/eabFe8He5UZiPu
$ docker run -p 5000:5000 --name registry -v /etc
13%
30.11.2025
08 default:
09 $(MAKE) -C $(KDIR) M=$(PWD) modules
10 endif
11
12 clean:
13 rm -rf *.ko *.o *.mod.c *.mod.o modules.order
14 rm -rf Module.symvers .*.cmd .tmp
13%
01.08.2019
_path": "/var/log/osquery",
07 "disable_logging": "false",
08 "schedule_splay_percent": 10
09 },
10 "schedule": {
11 "osquery_profile": {
12 "query": "SELECT * FROM osquery_info;",
13
13%
09.08.2015
resources = Resources(cpu = 0.1, ram = 20*MB, disk = 20*MB),
09 processes = [hello_world_process])
10
11 hello_world_job = Job(
12 cluster = 'test',
13 role = os.getenv('USER'),
14 task = hello
13%
11.04.2016
: /bin/false
06 tags: notworking
07 - name: Test Block 2
08 command: /bin/true
09 tags: working
10 rescue:
11 - debug: msg="error error error"
12 always:
13
13%
07.06.2019
better system protection, you can set the node monitor to "respawn" if it ever shuts down for any reason (notification email is recommended).
The OS for the test environment is Red Hat Enterprise Linux 7.3
13%
20.03.2014
": 2048,
07 "resolvers": ["192.168.111.254"],
08 "disks": [
09 {
10 "image_uuid": "1fc068b0-13b0-11e2-9f4e-2f3f6a96d9bc",
11 "boot": true,
12 "model": "virtio"
13 }
14 ],
15
13%
21.08.2014
and production.
To show how monitoring profiles can be implemented for a specific server, the example distinguishes between mail, web, and database servers. It assumes that the stable version 1.12.3 of OpenNMS [6
13%
30.11.2025
: 1331404720 TZ: -0500
09 # SubSys: bcdfijmnstYZCD Options: cz Interval: 10:60 NumCPUs: 4 NumBud: 3 Flags: ix
10 # Filters: NfsFilt: EnvFilt:
11 # HZ: 100 Arch: x86_64-linux-thread-multi PageSize: 4096
12 # Cpu
