21%
12.11.2013
community to continue development of an independent fork named Bareos.
The first stable release was Bareos 12.4 in April 2013 (the version number stands for the year and the quarter of the feature freeze
21%
21.07.2011
heartbeat = 1
07 heartbeat_port = 539
08 keepalive = 6
09 deadtime = 18
10 network = direct
11 debug_level = NONE
12 monitor_links = 1
13 syncdaemon = 1
14 virtual webs.test.com {
15 active = 1
16 ... 3
21%
10.06.2015
. The current version is Mesos 0.21.
Two years after the first release, the developers presented a far more advanced variant [3] at a 2011 Usenix conference. Twitter engineers had already been running Mesos
21%
22.12.2017
=> /lib64/libpthread.so.0 (0x00007f5bc524a000)
libpgc.so => /opt/pgi/linux86-64/16.10/lib/libpgc.so (0x00007f5bc4fc2000)
librt.so.1 => /lib64/librt.so.1 (0x00007f5bc4dba000)
libm.so.6 => /lib64
21%
14.01.2016
the registers and main memory, Level 1 (L1), Level 2 (L2), and even L3 and L4 caches have been added. Typically the L1 cache is part of the processor (each core) and can store more data than the registers
21%
03.12.2015
the registers and main memory, Level 1 (L1), Level 2 (L2), and even L3 and L4 caches have been added. Typically the L1 cache is part of the processor (each core) and can store more data than the registers
21%
02.06.2020
is a key part of securing an estate. Common Vulnerabilities and Exploits (CVEs) [3] are the most popular way of listing, publishing, and categorizing security bugs. Within Prisma Cloud Compute, you can
21%
30.11.2020
with the integrated system script:
sudo apt-get install openjdk-8-jre
wget http://pub.nxfilter.org/nxfilter-4.3.6.1.deb
sudo dpkg -i nxfilter-4.3.6.1.deb
sudo systemctl enable nxfilter
sudo systemctl start nxfilter
21%
18.07.2013
Lustre on top of ZFS [3] and reaching about 850GBps. Marc talked about moving data from older systems to Sequoia and some of the issues the team faced (it wasn't easy). His talk inspired me to examine
21%
09.04.2019
selected the wordpress:php7.2
and mysql:5.6
images (which I'll call the "production" deployment) from Docker Hub for my containers. To run it as a microservice, I deployed it as shown in Figure 3
