The suggestion to do the following in /etc/init.d/openafs-client had been working great until some update in squeeze a few weeks ago.
>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? Brent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
