9%
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
9%
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
9%
11.06.2014
was also available in the form of X.500, but it was not very widespread in practice. LDAP was originally designed as a protocol for X.500 services. This mutated into the LDAP directory servers that are seen
9%
05.03.2014
on weekdays costs no less than 9,000 Euros, while the same cluster with 24x7 support is priced at 14,000 Euros. Realistically, however, no one will operate cloud storage with only two nodes; assuming you have
9%
07.10.2014
; only your explicitly allowed IP addresses present in /etc/hosts.allow can get that far.
Another useful precaution is to kick people off the server who have been idle for 20 minutes (i.e., 1,200 seconds
9%
02.02.2021
.sin(periods * 2 * np.pi * t)
12 return max(value, 0.0)
13 else:
14 value = np.sin(periods * 2 * np.pi * t)
15 return max(value, 0.0)
16
17 # building the data vector
18 my_data = []
19 i = 0
20 while
9%
07.07.2025
or incorporated into scripts.
Introduction to Logger
All of the examples in this article are from a rather dated Ubuntu 20.04 system, although logger
works the same way on current distributions. The basic syntax
9%
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
9%
12.02.2014
to measure the 15-minute node load average every few seconds? If the application takes 12 hours to run, do you need to measure the CPU load every two to three seconds? The main result of frequent monitoring
9%
11.04.2016
/iptables -X -t nat
12 /sbin/iptables -X -t mangle
13 /sbin/iptables --flush FORWARD
14 /sbin/iptables --flush INPUT
15 /sbin/iptables --flush OUTPUT
16
17 #exit
18
19 #policies for the chains
