13%
18.07.2013
backend3.example.com server;
05 backend4.example.com server down;
06 backend5.example.com backup server;
07 }
08
09 upstream fallback {
10 fallback1.example.com server: 8081;
11 }
12
13
14 server {
15 %
16
13%
20.03.2014
": 2048,
07 "resolvers": ["192.168.111.254"],
08 "disks": [
09 {
10 "image_uuid": "1fc068b0-13b0-11e2-9f4e-2f3f6a96d9bc",
11 "boot": true,
12 "model": "virtio"
13 }
14 ],
15
13%
01.08.2019
.
Listing 4
Registry Configuration
01 version: 0.1
02 log:
03 fields:
04 service: registry
05 storage:
06 filesystem:
07 rootdirectory: /var/lib/registry
08 http:
09
13%
05.02.2019
SQL> SELECT * FROM marks;
11
12 SQL> DELIMITER //
13
14 SQL> CREATE AGGREGATE FUNCTION agg_count(x INT) RETURNS INT
15 BEGIN
16 DECLARE count_students INT DEFAULT 0;
17 DECLARE CONTINUE HANDLER
13%
30.04.2013
of the memory:
dd if=/dev/fmem of=memory.dd bs=1MB count=512
Another tool for dumping memory is the kernel module crash
, which was developed by Red Hat. Just like fmem
, crash
creates a pseudodevice called
13%
22.08.2011
[inst.id] = inst.state
08 summary[inst.state] += 1
09 state
10 end
11 total = summary.values.inject(0) { |sum, i| sum += i }
12 puts "Found #{total} instances in the following states:"
13 summary
13%
13.12.2018
"$file" ]; then
05 touch /tmp/listner.log
06 fi
07 tail -n 0 -F /db/oraclese/product/diag/tnslsnr/pics-db11/listener/trace/listener.log | while read LINE
08 do
09 echo "\"host:\" "\"picsdb\", \"message
13%
31.05.2012
.77
4.11
mandel
5.55
31.15
65.44
824.68
156.68
5.67
pi_sum
0.74
18.03
1.08
328.33
164.69
0.75
rand
13%
29.09.2020
.168.2.17",
04 "visible": true,
05 "color": "green",
06 "user": "root"
07 },
08 "web server": {
09 "address": "192.168.2.4",
10 "visible": true,
11 "color": "rgb(100, 200, 0)",
12
13%
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
