Tag Info

Hot answers tagged

7

I would create a separate specific passwordless SSH key for this purpose. On the server side, you can set limits to what that key can be used for and where it can connect from, so that even if someone gets hold of the key, they would still not be able to use it to do something malicious. The way to limit the key is to edit the authorized_keys file on the ...


4

You can use SSH keys which have no passphrase. If you don't like that idea then you can create a key file without passphrase and put it into a RAM disk. Thus after a reboot you would have to log in manually in order to prepare the system for batch SSH usage by entering the passphrase and providing the new file. In the ssh calls you would have to provide ...


2

The README in that directory states that scripts in that directory are only called once on poweroff (and not on reboot). With a simple test program #!/bin/bash LOG=/root/backup.log date >> $LOG echo $* >> $LOG I noticed that one time the program was actually called twice, once without a parameter and once with the parameter 'stop'. I have ...


2

I think that ntfsclone might be really helpfull here. As mentioned in the manuall: "...ntfsclone can be useful to make backups, an exact snapshot of an NTFS filesystem and restore it later on..." ntfsclone is part of the ntfs-3g package.


1

This already does a full backup. The contents of the directories that are excluded (such as dev, run, etc) are created in run time and should not be backed up. Copying boot folder will not override your boot sector, so that is fine. Using rsync here is the correct method as rsync can work within the same system or remotely and it will also only update ...


1

Take a look at the keychain package. I'm not sure if it will do what you want, but it does cache the keys in memory in some fashion. And it does not require X to work.


1

The "solution" you mention is a really bad one (it can't deal with weird file names for example) and completely unnecessary. Just use diff directly: diff -r "$PATH1" "$PATH2" That will recursively (-r) compare the directories and report whether files are present or missing. For example: $ tree . ├── dirA │   ├── file1 │   └── file2 └── dirB └── ...



Only top voted, non community-wiki answers of a minimum length are eligible