> > The problem was: The machine where s3ql is running is a DNS and DHCP > server for the network (by the way these services are managed by the > Zentyal Domain Controller). When the s3ql service is started, the network > is ready, but dns is not.
Since I couldn't find the service for the DNS, I used the DHCP service like this: start on (filesystem and net-device-up IFACE=p119p1 *and started isc-dhcp-server*) which works now. The --lazy option has nothing to do with the problem, since it only has influence when the service is shutting down, which was not the case. Thanks. -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
