17%
17.01.2023
modified mine to keep it really simple:
server 2.rocky.pool.ntp.org
driftfile /var/lib/chrony/drift
makestep 1.0 3
rtcsync
allow 10.0.0.0/8
local stratum 10
keyfile /etc/chrony.keys
leapsectz
17%
22.06.2012
0-07:06:40
10
32400
0-09:00:00
11
40000
0-11:06:40
12
48400
0-13:26:40
13
57600
0-16:00:00
14
67600
17%
05.12.2019
priority at 3:45 daily except Sundays
## and inform user 'jim' about it. Process job after startup
## if the PC was not running at the scheduled time.
&nice(10),mailto(jim),bootrun 45 03 * * *~0 "save --our
17%
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
17%
23.07.2012
for brevity]
8 10.59 so-4-2-0.mpr3.pao1.us.above.net (64.125.28.142)
9 11.00 metro0.sv.svcolo.com (208.185.168.173)
10 9.93 scanme.nmap.org (64.13.134.52)
Nmap
17%
31.10.2025
ADDRESS
[Cut first seven hops for brevity]
8 10.59 so-4-2-0.mpr3.pao1.us.above.net (64.125.28.142)
9 11.00 metro0.sv.svcolo.com (208.185.168.173)
10 9
17%
14.03.2018
that can be reset. However, with MariaDB 10.0.12, the performance tables are deactivated by default. To activate them, the database admin adds the line
performance_schema=on
to the my.cnf file. Detailed
17%
05.02.2019
:
$ curl http://169.254.169.254
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
The cloud-init
package installed on an instance contains utilities for its early
17%
18.12.2013
(One-by-One)
1 #include
2
3 /* Our structure */
4 struct rec
5 {
6 int x,y,z;
7 float value;
8 };
9
10 int main()
11 {
12 int counter;
13 struct rec my_record;
14 int counter_limit;
15
17%
18.07.2013
in TLSv1.0 was error-prone, but the problems long remained theoretical.
TLSv1.1, which was designed to iron out the worst weaknesses of CBC, followed in 2006. Two years later, TLSv1.2 was released
