24%
04.12.2013
3 type rec
4 integer :: x, y, z
5 real :: value
6 end type rec
7
8 integer :: counter
9 integer :: counter_limit
10 integer :: ierr
11
12 type (rec) :: my
24%
11.06.2014
at the bottom of the window, ranges from 0 (less risky) to 100 (more risky). Because these two processes started after the malware installed, they are likely bad. When I compared the Start Time of svchost
24%
11.10.2016
-server"}))
06
07 ; Enable all interfaces for TCP, UDP and websockets:
08 (let [host "0.0.0.0"]
09 (tcp-server {:host host})
10 (udp-server {:host host})
11 (ws-server {:host host}))
12
13 ; Clean up events
24%
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
24%
14.11.2013
distributions.
Table 1
Udev Storage Locations
Distribution
Path
Ubuntu 12.10, Debian 7.0, SLES 11 SP2
* /etc/udev/rules.d/70-persistent-net.rules* /lib/udev/rules.d/75
24%
05.12.2016
the user input
# Set bold mode
tput bold
tput cup 10 15
read -p "Enter Your Choice [1-2] " choice
tput clear
tput sgr0
tput rc
Figure 3: tput sample
24%
16.08.2018
pdsh read the hosts from a file other than the WCOLL environment variable:
$ 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
24%
14.03.2013
will be using the Mongo shell to create a document (Listing 1).
Listing 1
Test
01 # mongo
02 MongoDB shell version: 2.2.0
03 connecting to: test
04 > use football
05 switched to db football
06 > db
24%
04.11.2011
$if | bzip2 ‑9 > $if.bz2;
04 done
05 real 0m27.005s
06 user 0m11.745s
07 sys 0m14.623s
08
09 $ time find . ‑name "*.gz" ‑print | parallel ‑j +0 'zcat {} | bzip2 ‑9 > {.}bz2'
11
12 real 0m
24%
14.03.2013
signatures. And the successors of SSL, TLS 1.0 and 1.1, do not improve on this; it is not until TLS 1.2 that TLS began to support newer algorithms with SHA-2.
On the server side, you need version 1.0
