micah a écrit (07 Nov 2005 23:13:33 +0100) :
The only way a cronjob could use your ssh-agent is if it was
launched from a shell that was created after the agent was
launched. Cron stuff generally runs as root however, so you would
have to have a ssh-agent for root and restart crond after
Package: backupninja
Version: 0.9-1
backupninja -t -n succeeds, but scheduled backups don's. They produce
the message:
*failed* -- /etc/backup.d/90.rdiff
== fatal errors from /etc/backup.d/90.rdiff ==
Fatal: Can't connect to dest-host as dest-user.
I noticed that the helper script uses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ahmad Khayyat wrote:
Package: backupninja
Version: 0.9-1
backupninja -t -n succeeds, but scheduled backups don's. They produce
the message:
*failed* -- /etc/backup.d/90.rdiff
== fatal errors from /etc/backup.d/90.rdiff ==
Fatal: Can't
1. That was my substituation.. consider those as
variables.
2. Is there any means by which I can provide the passphrase to the
scheduled backups?
It seems that thay do not run in the current logged-in session,
otherwise they could have used the session's ssh agent.
micah wrote:
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ahmad Khayyat wrote:
1. That was my substituation.. consider those as variables.
2. Is there any means by which I can provide the passphrase to the
scheduled backups?
It seems that thay do not run in the current logged-in session,
otherwise
5 matches
Mail list logo
