17%
12.09.2013
: 1.0
05 Release: 1%{?dist}
06 License: GPL v2 or later
07 Source0: local.te
08 Source1: local.fc
09 Source2: local.if
10 Group: Development/Tools
11 Summary
17%
20.06.2022
_ADMIN=admin
10 - KEYCLOAK_ADMIN_PASSWORD=SOME_PASSWORD
11 - KC_DB=postgres
12 - KC_DB_URL=jdbc:postgresql://postgres:5432/keycloak
13 - KC_DB_USERNAME=postgres
14 - KC
17%
28.11.2021
edit podman.socket
08 mkdir -p /etc/systemd/system/podman.socket.d
09 cat >/etc/systemd/system/podman.socket.d/override.conf
10 [Socket]
11 SocketMode=0660
12 SocketUser=root
13 Socket
17%
28.11.2021
_interval: 10s
09 receiver: 'email'
10 receivers:
11 - name: 'email'
12 email_configs:
13 - to: 'helpdesk@mycompany.com'
14 from: 'monitoring@mycompany.com'
15 smarthost: smtp.mycompany.com:587
16
17%
07.06.2019
${WORK_DIR}
10 VOLUME ${WORK_DIR}
11
12 COPY Debian/stretch-backports.list /etc/apt/sources.list.d/
13 COPY Debian/testing.list /etc/apt/sources.list.d/
14
15 RUN apt-get update -y \
16 && apt-get upgrade
17%
09.01.2013
on = "STOP",
10 command = "account.sh",
11 arguments = "off $ID" ]
12 [...]
Listing 2
/var/lib/one/remotes/hooks/acccount.sh
01 #!/bin/bash
02
03 ACCOUNTING
17%
07.06.2019
version 10.4 to version 12.3. A safe version range, then, would be to stay within version 10.4. Of course, it's entirely up to you what risks to take and what you consider a safe version range.
To update
17%
18.07.2013
in TLSv1.0 was error-prone, but the problems long remained theoretical.
TLSv1.1, which was designed to iron out the worst weaknesses of CBC, followed in 2006. Two years later, TLSv1.2 was released
17%
07.10.2014
; restarting.
Aug 19 18:10:43 localhost sshd[3328]: Server listening on 0.0.0.0 port 22.
Aug 19 18:10:43 localhost sshd[3328]: Server listening on :: port 22.
Not on the List
The next thing I'll discuss
17%
05.12.2019
()
bootrun(true)
Runs a job after starting fcron or booting the system.
jitter()
jitter(10)
Delay job by up to 255 seconds if multiple jobs start at the same time
