19%
05.08.2024
/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.11.2 (main, Feb 17 2023, 09:48:02) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)] (/usr/bin/python3.11)
jinja version = 3.1.2
libyaml = False
19%
14.03.2013
/myclubs.json
connected to: 127.0.0.1
Mon Dec 3 08:43:26 imported 23 objects
It is also very easy to query an object via a specific field (Listing 2).
Listing 2
Query
01 > db.clubs.find({Members: {"$gt
19%
10.04.2015
.10 Node.js 0.10 web
09 perl-5.10 Perl 5.10 web
10 php-5.3 PHP 5.3 web
11 php-5
19%
01.08.2019
. The takeaway is the -j LOG option (line 12), which logs port scanning behavior to a logfile with the iptables:
prefix.
Listing 1
iptable Rules
01 *filter
02 *filter
03 :INPUT ACCEPT [0:0]
04
19%
04.08.2020
// (c) 2020 by Federico Lucifredi
04
05 #include
06 #include
07 #include
08 #include
09 #include
10 #include
11 #include
12
13
19%
07.06.2019
--retry 3 --retry-delay 0 --retry-max-time 60 ${JENKINS_UC}/jenkins.war -o ${JENKINS_HOME}/jenkins.war
30 RUN for P in ${PLUGINS}; do curl -sSfL --connect-timeout 20 --retry 2 --retry-delay 0 --retry
19%
21.08.2014
/origin/HEAD -> origin/master
09 remotes/origin/android-goldfish-2.6.29
10 remotes/origin/android-goldfish-3.4
11 remotes/origin/linux-goldfish-3.0-wip
12 remotes/origin/master
13 [...]
14 [root@pc]# git checkout
19%
14.03.2018
– comparable to setting an interface route with:
ip route add 1.2.3.0/24 dev eth0
Conversely, the external VPC must know how to find the internal VPC, which requires routes to the internal subnet and also
19%
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
19%
13.12.2018
_64 2/4
08 Installing : gdb-7.6.1-110.el7.x86_64 3/4
09 Installing : mssql-server-14.0.3026.27-2.x86
