11%
13.12.2018
remember using it at Linux Networx in the early 2000s. Over the years, it has been developed by Lawrence Livermore National Laboratory, SchedMD [5], Linux Networx, Hewlett-Packard, and Groupe Bull [6
11%
11.06.2014
# replace: olcRootDN
07 dn: olcDatabase={2}bdb,cn=config
08 changetype: modify
09 replace: olcRootPW
10 olcRootPW: {SSHA}f0pv70XFFox5UqKc6A4Uy39NcxkqcJbc
11 -
12 replace: olcAccess
13 olcAccess: {0}to attrs
11%
10.09.2012
to logfiles, and it’s pretty simple to use:
[laytonjb@test1 ~]$ logger "This is a test"
...
[root@test1 ~]# tail -n 2 /var/log/messages
Aug 22 15:54:47 test1 avahi-daemon[1398]: Invalid query packet.
Aug 22 17
11%
18.03.2013
is a classic bug in a web application: an SQL injection vulnerability. SQL injection, which has been known for around 12 years, is still one of the hacker’s most popular tools.
This article presents real
11%
14.03.2013
is a classic bug in a web application: an SQL injection vulnerability. SQL injection, which has been known for around 12 years, is still one of the hacker's most popular tools.
This article presents real
11%
25.03.2020
, according to the README file, requires "half the memory, all in a binary less than 40MB" to run. By design, it is authored with a healthy degree of foresight by the people at Rancher [3]. The GitHub page [4
11%
02.06.2020
754 pages of about 63MB) with details on where to find the latest release. In my case, this was version 19.11.480. The docs are also now public, which is more convenient (an access token attached
11%
22.05.2023
, on the secondary node, enter:
$ watch -n1 cat /proc/drbd
You should see something similar to the output shown in Listing 3. When synchronization is 100 percent complete, the same file will showcase the output
11%
08.10.2015
was possible in principle, but this solution was not as clean as developing a separate interface. This need for a container interface is precisely the gap that Magnum [6] [7] sets out to fill. As a new Open
11%
14.03.2013
revealed in 2012. The Flame virus contained a valid Microsoft code signature [6] and was thus able to propagate via the Windows Update Service. The precise details of the attack are unknown
