Hi.
Is there a possibiliry to delay a job from a passive client?
I have a job defined simply like this:
Job {
  Name = "laptop"
  JobDefs = "DefaultJob"
  Schedule= "EarlyWeeklyCycle"
  Fileset = "LinuxDocs"
  Client = "laptop-fd"
  Priority = 5
  Run On Incoming Connect Interval = 12h
}
The client here has "connection from client to director=yes"

It's as simple as it gets.
And it works pretty good. The problem is that by default the laptop 
connects to wifi on power on and while it's OK for most times, sometimes 
(especially when I want to do the full backup) I want to have it connected 
with cable ethernet. The problem is that right after the power on the FD 
starts, connects to the director and the backup job is spawned. And if I 
switch my connection from the default wifi to cable, the job is left 
hanging on both sides (FD and dir) and I have to restart both the FD and 
director. It's not pretty.
I'm wondering if I can do something to make it all more robust.

MK

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/cb6b8767-f9bc-4802-b96a-7d6658140606n%40googlegroups.com.

Reply via email to