28%
23.07.2012
purpose
Running: Linux 2.6.X
OS details: Linux 2.6.20-1 (Fedora Core 5)
TRACEROUTE (using port 80/tcp)
HOP RTT ADDRESS
[Cut first seven hops
28%
31.10.2025
closed auth
Device type: general purpose
Running: Linux 2.6.X
OS details: Linux 2.6.20-1 (Fedora Core 5)
TRACEROUTE (using port 80/tcp)
HOP RTT
28%
02.07.2014
:
[laytonjb@home4 ~]$ pdsh -w 192.168.1.250 uname -r
192.168.1.250: 2.6.32-431.11.2.el6.x86_64
The -w
option means I am specifying the node(s) that will run the command. In this case, I specified the IP
28%
21.08.2012
/var/chroots/sl6.2/etc/rc.d/rc.local
):
[root@test1 rc.d]# more rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff
28%
05.02.2023
You can also use exactly the same principle to create stateful sets for PostgreSQL or Microsoft SQL servers in containers. For PostgreSQL, use port 5432 instead of 3306 and the postgresql
28%
05.02.2023
--name yb2 --hostname yb2 --net=yb -p5432:5433-p7002:7000 yugabytedb/yugabyte:latest yugabyted start --daemon=false --listen yb2 --join yb1
$ docker run -d --name yb3 --hostname yb3 --net=yb-p5433:5433 -p
28%
10.04.2015
; Figure 3) [6], and Project Atomic, "a lean and mean OS built for containers" [7] looks promising, despite the beta state. If you want to dive deeper into the underlying technology, the OpenShift blog
28%
20.06.2012
is to find out whether it runs on the master node when it is booted by using the chkconfig
command:
[root@test1 etc]# chkconfig --list
...
nfs 0:off 1:off 2:off 3:off 4:off 5:off 6
28%
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
28%
31.10.2025
of important features). All of the NAS devices in our lab used Intel processors and supported popular RAID levels, at least 1 and 5; the better devices also offered a dual-parity variant like RAID 6. (See
