On 02.12.2016 at 19:32 wrote Peter Zingg:
> I am starting to roll out Bareos at our school district office and
> will be backing up multiple Mac clients. (Using the "experimental"
> Mac file daemon).  The only problem I currently have is that if the
> file daemon quits (maybe because Mac goes to sleep or some other
> issue), it won't restart properly.
> 
> The error message is "Working Directory: "/var/run/bareos/working"
> not found. Cannot continue."
> 
> Apparently /var/runbareos/working gets removed and the file daemon
> does not try to re-make it. Any suggestions? One workaround I have is
> to write a wrapper script that creates the directory before the
> daemon is started, or maybe specify a "WorkingDirectory" in the
> bareos-fd.conf file that would not be subject to removal.

Both options are possible. We will fix this issue in the next release.

Jörg

-- 
 Jörg Steffens                   joerg.steff...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-91
 http://www.bareos.com           Fax:   +49 221 630693-10

 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer:
 S. Dühr, M. Außendorf, Jörg Steffens, P. Storz

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-devel+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-devel@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to