On Tuesday, November 13, 2018 at 8:47:41 AM UTC-6, Raymond Norton wrote:
> My new Bareos setup is working fine but jobs stack up when a client PC is
> down. I would like for Bareos to try 5 minutes or less and move on to the
> next job. I added FD Connect Timeout 1 to the dir config but it did not seem
> to change things.
>
> Running 18.2 for the server and 17.2 for a client (linux)
I still have not figured out how to force the director to cancel a job when it
cannot connect to a client and move on to the next job. My .conf file indicates
it should run up to 10 concurrent jobs.
Director { # define myself
Name = bareos-dir
QueryFile = "/usr/lib/bareos/scripts/query.sql"
Maximum Concurrent Jobs = 10
Password = "password" # Console password
Messages = Daemon
Auditing = yes
FD Connect Timeout = 1
I added the FD Connect timeout but that does not work either.
Ideas?
--
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 [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
