15%
30.11.2025
_dlm]
root 3467 7 0 20:07 ? 00:00:00 [o2net]
root 3965 7 0 20:24 ? 00:00:00 [ocfs2_wq]
root 7921 7 0 22:40 ? 00:00:00 [o2hb-BD5A574EC8]
root 7935 7
14%
17.02.2015
service_description PING
11 check_command check_ping!100.0,20%!500.0,60%
12 }
13 define service{
14 use generic-service ; Name of service template to use
15
14%
15.08.2016
1.1.1.1/10 scope global veth1 valid_lft forever preferred_lft forever
$ ss -etn
State Recv-Q Send-Q Local Address:Port Peer Address:Port
ESTAB 0 0 1.1.1.1:22 1
14%
25.01.2022
17 lvm_vs_md_tar.gz 1365 sandforce.tar.gz
22 et4_64GB_journal.txt 0 MD_ARTICLE 0 SMARTMONTOOLS
4 ext2_defaults.txt.gz 0 MD_ARTICLE_2 4 squashfs
14%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
14%
12.05.2020
):
root@c31656cbd380:/# apt-get update
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
...
Fetched 18.0 MB in 9s (1960 kB/s)
After the package repositories are synced, I can
14%
30.11.2025
were run on a virtual system (using ESX as the hypervisor) with fixed reservations for CPU and memory. To be more precise, I used a virtual CPU running at 1.5GHz and with 512MB of RAM in the virtual
14%
02.07.2014
WCOLL points:
[laytonjb@home4 ~]$ pdsh -w ^/tmp/hosts uptime
192.168.1.4: 15:51:39 up 8:35, 12 users, load average: 0.64, 0.38, 0.20
192.168.1.250: 15:47:53 up 2 min, 0 users, load average: 0.10, 0.10, 0
14%
18.07.2013
=> present,
11 source => 'puppet:///modules/myproject/apache/000-default',
12 owner => 'root',
13 group => 'root',
14 mode => '0664',
15 require => Package['apache'],
16 notify
14%
01.08.2019
are removed from DNS
# answers. Additionally, the DNSSEC validator may mark the answers bogus.
# This protects against DNS Rebinding
private-address: 10.0.0.0/8
private-address: 172.16.0.0/12
