Here are two possible solutions: * Make the tunnel at startup (e.g. in the script that starts bacula-dir).
* Use something like inetd to make an ssh connection on-demand (e.g. like https://capocasa.net/on-demand-ssh-port-forwarding-with-inetd). __Martin >>>>> On Fri, 11 Jan 2019 20:55:04 +0100, PenguinWhispererThe said: > > Hi, > > What I'm trying to do feels obvious but I can't find what I'm looking for. > > I have a client that's remote. The connectivity to the remote client is > established through an SSH script. > In general the SSH connection is up or re-established when a job runs > through Run Before Job in a JobDefs piece. > This works properly. > > Once in a while I want to retrieve the status of the client. This > frequently times out and the cause seems to be that the Run Before Job is > not being executed (which is obviously as designed). > Now I'd like to know if there's a way to start a script every time you > connect to the client. > I've checked the documentation on the Client definition but couldn't see > anything that fits my needs. > > How could I make this work? Or what is the configuration to accomplish this? > > Thanks in advance. _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
