In some special cases is a VM accessible over NAT and on different port as usually 22.
In this case – SSH is running on port 222.
This make the rsync operation little bit complexer:
1 | rsync -vraze 'ssh -p 222' root@remote:/source/ /destination/ |
In some special cases is a VM accessible over NAT and on different port as usually 22.
In this case – SSH is running on port 222.
This make the rsync operation little bit complexer:
1 | rsync -vraze 'ssh -p 222' root@remote:/source/ /destination/ |
rsync -vraze 'ssh -p 222' root@remote:/source/ /destination/
Mac OS X has a kind of different client behavior with a SMB-Server (Samba 3.6.6-6) than a Windows client.
By saving new files, they will be stored with Mask “0600/-rw——-” and that doesn’t matter what samba configuration prescribes (force create mode = 777).
So the explanation for this problem was found in the SAMBA documentation:
SAMBA has the “unix extensions” option set to “on” by default. This allows Unix users who write to the Samba shares to set their own permissions bits.
Now set them in the SAMBA global section [1] to off:
1 | unix extensions = no |
unix extensions = no
[1] SAMBA configuration file: /etc/samba/smb.conf
If you need to change the hostname of an existing munin node with a lot of data, and you want to retain all this existing historical data, follow this procedure:
[Read more…]
Migration from Freenas all ZFS volumes to another machines lvm is pretty simple.
create on you new machine logical volume and start netcat which will write everything it receives to the new LVM of your choice:
# Source box
1 | dd bs=16M if=/dev/disk/by-path/iscsi-mysql-lun-0 | nc 192.168.1.254 19000 |
dd bs=16M if=/dev/disk/by-path/iscsi-mysql-lun-0 | nc 192.168.1.254 19000
# Destination box (192.168.1.254)
1 | nc -l -p 19000|dd bs=16M of=/dev/vg0/mysql-data |
nc -l -p 19000|dd bs=16M of=/dev/vg0/mysql-data
While signing a certificate for a new OpenVPN user, I received the following error message which stops the whole process (exit code 1)
Certificate is to be certified until Nov 6 08:53:05 2023 GMT (3650 days)
Sign the certificate? [y/n]:y
failed to update database
TXT_DB error number 2
Problem:
Because you have generated your own self signed certificate with the same CN (Common Name) information that the CA certificate that you’ve generated before.
Enter another Common Name.