Hello Jesse, On Tue, 26 Jul 2005 13:32:37 -0700 Jesse Keating <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-07-26 at 13:21 -0700, Jesse Keating wrote:
> > Wait, I'm on to something here. The ssh process goes away almost
> > immediately when called by Run Before Job. If I run it myself it
> > stays
> > running. Thoughts?
> >
>
> And I'll reply to myself one more time. In fact, if i call the ssh
> script outside of bacula, issue the back, then call the script to stop
> the tunnel it works like a charm. So for some reason, when the script
> is ran in Run Before Job it kills the script immediately. So, maybe a
> bit more debugging is in order....
I am doing exactly what you are trying to achieve. One thought I was
struggeling when using an ssh-tunnel.
I had to redirect the output of the ssh-command to /dev/null
(> /dev/null) in order to make the RunBeforeJob-directive work properly.
Perhaps this is your problem as well?!
I also needed to make sure that the user which running bacula (bacula,
on Suse8.0) has the ability to open an ssh-tunnel and vis versa. I
did that by creating ssh-keys for the user bacula and copied them to
the remote machine.
For a more verbose output you can add -v to the ssh-command
inside the script.
hth
Best
Stephan
--
Stephan Holl
Check headers for GnuPG Key!
http://www.gdf-hannover.de
pgpnDhH4OhbGT.pgp
Description: PGP signature
