9%
30.01.2020
]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=655Mi
9%
30.11.2025
) with 12 Serial ATA disks, a 320 UW SCSI controller for the host connection, and 512MB cache.
I configured various disk groups and logical volumes on this powerful hardware and exported them to the backup
9%
25.03.2020
/share/doc/stunnel*/. The example in Listing 1 shows a very simple configuration that uses stunnel as a plain vanilla TLS client.
Listing 1
Stunnel as a TLS Client
; global settings
sslVersion = TLSv1.2
chroot = /var
9%
16.08.2018
the potential for optimization.
A standard Let's Encrypt certificate has a key length of 2,048 bits and uses SHA256/RSA as the signature algorithm. Without any further changes to the parameters
9%
30.11.2025
dh_group modp1024;
09 }
10 generate_policy off;
11 }
12
13 sainfo address 192.168.2.0/24 any address 172.16.0.0/16 any {
14 pfs_group modp1024;
15 encryption_algorithm aes256;
16
9%
05.08.2024
your very first Ansible controller, the IBM Redbook, Using Ansible for Automation in IBM Power Environments
[12], is a great reference; particularly section 3.3, "Installing your Ansible control node
9%
10.06.2015
key
RSA
EIGamal
DSA
Cipher
IDEA
3DES
CAST5
Blowfish
AES-128/-192/-256
Twofish
Camellia-128/-192/-256
Hash
MD5
9%
25.10.2011
-256-cbc;
07 }
08 policy pfs2-aes256-sha1 {
09 perfect-forward-secrecy {
10 keys group2;
11 }
12 proposals aes256-sha1;
13 }
14 vpn racoonvpn {
15 bind
9%
24.02.2022
mount opts: user_xattr,errors=remount-ro
Parameters:
checking for existing Lustre data: not found
device size = 48128MB
formatting backing filesystem ldiskfs on /dev/sdb
target name testfs:MDT0000
kilobytes 49283072
9%
07.04.2022
_time update )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:
checking for existing Lustre data: not found
device size = 48128MB
formatting backing filesystem ldiskfs on /dev/sdb
target
