24%
25.09.2023
="chmod
---
> RQRDCMNDS="apt-get
> chmod
13a17
> mkdir
15a20
> usermod
35c40
< if ! wget "https://mmonit.com/monit/dist/binary/${MONITVER}/monit-${MONITVER}-linux-x64.tar.gz" -O /tmp
24%
25.10.2011
}
11 }
12 from-zone trust to-zone vpn {
13 match {
14 source-address trustnet;
15 destination-address remotelan;
16 application any;
17 }
18 then {
19 permit;
20
24%
05.02.2019
in the container?
20 - name: "mysql client exists"
21 path: '/usr/bin/mysql'
22 shouldExist: true
23
24 # Does the MySQL configuration file exist at the right place?
25 - name: "my.cnf exists and has appropriate
24%
11.06.2014
objectClass: person
20 objectClass: organizationalPerson
21 objectClass: inetOrgPerson
22 objectClass: posixAccount
23 cn: Ulrich Habel
24 gidNumber: 100
25 homeDirectory: /home/uhabel
26 sn: Habel
27 uid
24%
09.10.2017
in turn stores as a separate time series. The software can already cope with millions of time series, yet version 2.0 [6] should cover more extreme Kubernetes environments with thousands of nodes
24%
02.08.2022
be turned on and off according to what you want to check about the state of the node.
Almost 20 years ago, when I worked for a Linux high-performance computing (HPC) company that no longer exists, we had
24%
15.04.2013
standard. In October of 2012, the winner was chosen: the Keccak algorithm, which was developed by a team of Belgian scientists. This is the second competition of this type: The symmetrical encryption
24%
11.02.2016
your tuning actions. Are you looking for a shorter response time or more throughput? One objective could be, say: "Action X
takes 3.5 seconds to complete after clicking – in future, we want to be done
24%
14.11.2013
. This translates to Google's experiencing about 25,000-75,000 correctable errors (CE) per billion device hours per megabit, which translates to 2,000-6,000 CE/GB-yr (or about 250-750 CE/Gb-yr). This is much higher
24%
11.09.2018
- containerPort: 80
19
20 ---
21
22 apiVersion: v1
23 kind: Service
24 metadata:
25 name: nginx-svc
26 labels:
27 run: nginx-svc
28 spec:
29 type: NodePort
30 ports:
31 - port: 80
32 protocol
