"Brent S. Elmer Ph.D." <webe...@aim.com> writes: >>Try changing this line
>> # Should-Start: $syslog >>to look like this >> # Should-Start: $syslog $named >>I believe that will solve your problem. > I'm not sure what update broke it but now opanafs-client attempts to > start before dnsmasq is fully started. In the script I put in a ps to > see if dnsmasq is started and the ps shows that dnsmasq is started(at > least partially). I put in a ping to a url and it was unresolvable > which tells me that dnsmasq is not fully started. > Next I put in a sleep in a loop with the ping and eventually the ping > resolves presumably once dnsmasq fully starts. So, is the problem with > openafs not honoring the Should-Start or dnsmasq reporting that it is > started before it really is fully started? The latter, unfortunately, which makes this hard to fix. If the PIDs are in that sequence, the implication I think is that the dnsmasq init script returns as soon as it's forked off the process and doesn't wait for it to be fully running before passing control back to the init system saying that it had started a named. There may not be a good fix for this other than to add a sleep statement somewhere in the startup with a ping similar to what you describe, unless there's some way to get dnsmasq to report when it's actually done. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
