15%
31.10.2025
-----------------------------------------------------------------
15 | 0 | SELECT STATEMENT | 3130K | 833 |
16 |* 1 | HASH JOIN | 3130K | 833 |
17 |* 2 | TABLE ACCESS BY INDEX ROWID | SALES | 566K
15%
27.05.2025
including and after the &&, the output offers the version 0.4.13
very neatly, without any other characters. The part I commented out uses this VERSION variable in the URL to download dockle with curl, and
15%
27.05.2025
an executable Grml installation to a standard USB storage device in next to no time. If you want to do yourself a favor, grab a USB storage device with USB 3.0, which has long been standard.
As icing on the cake
15%
05.12.2014
among the integrated development environment (IDE) options available for R, I use RStudio [8]. I downloaded RStudio 0.98.1083 Debian 6+/Ubuntu 10.04+ (32-bit) and ran:
sudo dpkg -i rstudio-0.98.1083-i386
15%
09.04.2019
) service mesh. Although it uses the Envoy proxy (written in C++) as its default sidecar, it can optionally use Linkerd as its data plane. Version 1.1.0 was just released in March 2019. Istio 1.1 provides
15%
15.04.2014
client supplies testing123
here. To sum up, the configuration looks like this:
client localhost {
ipaddr = 127.0.0.1
secret = testing123
netmask = 32
}
The optional netmask
entry defines
15%
21.06.2013
under the GreenSQL radar and are not checked. But if you replace localhost with 127.0.0.1, everything should work as expected.
Back to School
While the permitted queries are known in principle for in
15%
30.04.2013
a server!")
And run it:
$ puppet apply myfile.pp
notice: Scope(Class[main]): Let's build a server!
notice: Finished catalog run in 0.01 seconds
Now create a simple and largely useless file in the same
15%
30.09.2013
nmap
as a cronjob once a day on a Linux machine to scan all the ports in a network range equivalent to a legacy Class B network:
/usr/bin/nmap -v -v -oG - -p 1-65535 10.1.0.0/16 > /tmp
15%
24.10.2011
and testing of the upgrade scripts (which update data files when such updating is required) has made it easier to upgrade from MySQL 5.0 to MariaDB 5.1 than from MySQL 5.0 to MySQL 5.1.
The standard policy
