14%
18.07.2013
says:
$ puppet apply .pp
notice: Scope(Class[main]): Let's build a server!
notice: Finished catalog run in 0.01 seconds
Next, create a simple and largely useless file in the same script, drop
14%
05.12.2014
2.
Listing 2
PatchStatsTop10.v.0.3.R
001 ## Server Owner Trend Analysis
002 ## -Missing Security Patches
003 ## Russ McRee, @holisticinfosec
004
005 library(XLConnect)
006 library
14%
14.11.2013
01 {
02 "name": "ONE-SCALE",
03 "deployment": "none",
04 "roles": [
05 {
06 "name": "appserver",
07 "cardinality": 2,
08 "vm_template": 0,
09
10 "min_vms" : 5,
11
14%
18.03.2012
Name
------- ------ ----- ----- ----- ------ -- -----------
81 9 2392 3076 76 0.12 3996 AmIcoSinglun64
74 9 1464 2568 42 0.09 2172 armsvc
195 10 2380 2984 62
14%
21.07.2011
address = 192.168.1.250 eth0:0
17 vip_nmask = 255.255.255.0
18 port = 80
19 send = "GET / HTTP/1.0\r\n\r\n"
20 expect = "HTTP"
21 use_regex = 0
22 load_monitor = rup
23 ... 3
14%
18.07.2013
no authentication. Also, the now quite old SSL version 3 is disabled. TLS version 1.0 has long been supported by all browsers, so activation of the old SSL versions should no longer be necessary.
Listing 2
14%
13.06.2016
to allow the no_root_squash option. A line for this purpose in /etc/exports would look like this:
/nfs 192.168.1.0/ 24(rw,no_root_squash)
It allows all the computers on the 192.168.1.0 network to mount
14%
07.10.2014
seq_timeout = 10
08 tcpflags = syn
09 command = /usr/sbin/iptables -A INPUT -s \
%IP% -p tcp --dport 22 -j ACCEPT
10
11 [closeSSH]
12 sequence = 9000
14%
11.06.2014
installation of Kolab 3.0 and later is a matter of one or two cups of coffee and does not impose too many requirements on the admin. The Kolab developers recommend a recent CentOS (preferably 6.4) as the basis ... Open standards and open source are requisite in Kolab groupware. The alpha release of version 3.1 hugely extended the number of compatible clients with the CalDAV and CardDAV protocols, making Kolab
14%
15.08.2016
) for client programs on request.
Division of Responsibilities
What initially sounds complicated proves to be remarkably simple in practice [3]. First, the developer describes the feature set of their REST API