28%
03.12.2015
2001:db8::201:203:409 prefixlen 64 scopeid 0x0
inet6 2001:db8::5555 prefixlen 64 scopeid 0x0
inet6 fe80::1:2ff:fe03:409 prefixlen 64 scopeid 0x20
ether 02
28%
14.03.2013
Franklin
Some big changes are happening in the processor world right now. For the past 15 years or so, both the HPC world and the enterprise world have settled on, for the most part, x86 as the
processor
28%
04.08.2020
(minified by 25.99X)
from python:2.7-alpine - 84.3MB => 23.1MB (minified by 3.65X)
from python:2.7.15 - 916MB => 27.5MB (minified by 33.29X)
from centos:7 - 647MB => 23MB (minified by 28.57X)
from centos ... DockerSlim minifies your Docker container images up to 30x and adds security, too.
28%
21.08.2014
of these operations can also have a heavy I/O component. The situation I'm familiar with was not that large in HPC terms – perhaps 12 to 20 nodes. However, it was just a "sample" problem. The complete problem would
28%
22.12.2017
up a software project. The process differs from one operating system to the next, but this article describes its use on Fedora 25, which first needs a couple of packages from the unofficial repository
28%
25.09.2023
="chmod
---
> RQRDCMNDS="apt-get
> chmod
13a17
> mkdir
15a20
> usermod
35c40
< if ! wget "https://mmonit.com/monit/dist/binary/${MONITVER}/monit-${MONITVER}-linux-x64.tar.gz" -O /tmp
28%
25.10.2011
}
11 }
12 from-zone trust to-zone vpn {
13 match {
14 source-address trustnet;
15 destination-address remotelan;
16 application any;
17 }
18 then {
19 permit;
20
28%
05.02.2019
in the container?
20 - name: "mysql client exists"
21 path: '/usr/bin/mysql'
22 shouldExist: true
23
24 # Does the MySQL configuration file exist at the right place?
25 - name: "my.cnf exists and has appropriate
28%
11.06.2014
objectClass: person
20 objectClass: organizationalPerson
21 objectClass: inetOrgPerson
22 objectClass: posixAccount
23 cn: Ulrich Habel
24 gidNumber: 100
25 homeDirectory: /home/uhabel
26 sn: Habel
27 uid
28%
09.10.2017
in turn stores as a separate time series. The software can already cope with millions of time series, yet version 2.0 [6] should cover more extreme Kubernetes environments with thousands of nodes
