18%
05.12.2019
print WRITEHANDLE "Here is some text";
11 close(WRITEHANDLE);
12 waitpid($processed, 0);
13 } else {
14 close(WRITEHANDLE);
15 while (defined($text = )) {
16 print $text;
17
18%
18.06.2014
- 112 days]: 8101 ( 2.09%) ( 25.12% cumulative)
[ 112- 168 days]: 47729 ( 12.30%) ( 37.42% cumulative)
[ 168- 252 days]: 3578 ( 0.92%) ( 38.34% cumulative)
[ 252- 365 days]: 4970
18%
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
18%
10.04.2015
"version": "3.0.0",
03 "watched": [
04 {
05 "path": "/opt/repos",
06 "triggers": [
07 {
08 "name": "repos-sync",
09 "command": [
10 "/usr
18%
06.10.2019
* argv [])
06 /*@requires maxRead(argv) >= 1 @*/
07 /*@-modfilesys@*/
08 {
09 /*@-initallelements@*/
10 char buffer [BUFSIZE] = {'\0'};
11 /*@+initallelements@*/
12 if ( ( argc
18%
09.01.2013
=/var/log/one/accounting.log
04
05 case "$1" in
06 "on"|"off")
07 mode=$1
08 shift
09 ;;
10 *)
11 echo "$0 error: wrong mode." >&2
12 exit 1
13 ;;
14 esac
15
16 if [ "$1
18%
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
18%
11.04.2016
-enterprise-3.8.1-ubuntu-14.04-amd64/packages/ubuntu-14.04-amd64
sudo dpkg -i pe-cloud-provisioner-libs_0.3.2-1puppet1_amd64.deb
sudo dpkg -i pe-cloud-provisioner_1.2.0-1puppet1_all.deb
vSphere Setup
After
18%
25.03.2020
_DATA=$1
06
07 # This is the Event Data
08 echo $EVENT_DATA
09
10 # Example of command usage
11 EVENT_JSON=$(echo $EVENT_DATA | jq .)
12
13 # Example of AWS command that's output will show up
18%
04.10.2018
with this expectation? Very much so (Figure 2). The simple benchmark built into the Gnome Disks tool yields a remarkably close 541.6MBps average read rate, with a stunning 0.09ms average latency (tested with 1
