network profile
| bio | website | wiki.apertium.org/wiki/… |
|---|---|---|
| location | Sandnes, Norway | |
| age | ||
| visits | member for | 1 year, 5 months |
| seen | May 15 at 13:50 | |
| stats | profile views | 0 |
natural language processor
|
Jan 17 |
comment |
rsync without password, none of google (server fault) tutorials worked You might want to PermitRootLogin without-password to be on the safe side (without-password means pubkey-only) |
|
Jan 17 |
comment |
Trying to setup chroot'd rsync You can use the perl script rrsync instead of rssh, included in the official rsync package. See derek.simkowiak.net/backing-up-multiple-servers-with-rsnapshot |
|
Jan 17 |
comment |
Backup Permissions for Entire File System You can use PermitRootLogin forced-commands-only with the rrsync perl script (included with rsync). See derek.simkowiak.net/backing-up-multiple-servers-with-rsnapshot (scroll down to where the sshd_config setup is) |
|
Jan 14 |
comment |
What effect does it have on a server when you kill all root processes? Just because a critical service is killed, doesn't mean the machine will go down immediately. I would e.g. consider my fan control daemon critical – when cpu usage goes up, I want the fan to spin more. I could kill the service and have low cpu usage for days, then suddenly 1000 people access my site and my cpu catches fire. And there are many more less noticable ways of doing damage … |
|
Jan 13 |
comment |
btrfs-enabled backup solution I'm also considering backing up to btrfs, but I was just thinking of rsync -a --delete /home/user /mnt/butterfs/backups/ && snapper create – apart from creating a snapshot after backing up, what do you mean by COW-aware? |
|
Jan 13 |
awarded | Supporter |
