On mardi, 2 février 2016 13.55:57 h CET David Pearce wrote: > I am running Bareos on a server that about once a month has a hardware event > the causes an instantaneous reboot with no proper shutdown. This is my > problem. > > However I have noticed that the processes bareos-fd and bareos-sd will > recover on reboot even though the PID file for each process still exists. > > The process bareos-dir will not start because the PID file still exists but > the process is NOT running. > > My local Linux guru tells me a process should not be using the existence of > the PID file ALONE to abort starting. Is should be making some other API call > to determine if it is safe to start. > > Comments? Certainly a good idea, to have the 3 daemons reacting the same. > I move my pid file to tmpfs, they will never block you after a reboot ;-)
I'm using a /etc/tmpfiles.d/bareos.conf d /run/bareos 2775 bareos bareos - and a copy of /usr/lib/systemd/system/bareos-*.service in /etc/systemd/system with PIDFile pointing to /run/ -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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.
