"Brent S. Elmer Ph.D." <[email protected]> writes: > I looked into the openafs-client init script. This is on my work > laptop. The init script is modified. Our AFS servers are on the > intranet and therefore openafs with my cells will only work if the > laptop is on the intranet.
Oh, okay. That would explain it. > So, it doesn't look like an openafs problem since the init script has > been modified. It would be nice though if I could figure out how to > make dnsmasq start first. If I could figure it out, would I have to > change it every time openafs-client or dnsmasq is updated? To make openafs-client start first depends on whether you're using dependency-based boot ordering. Given the start numbers I don't think you are. So, all you should have to do is, in /etc/rc[2345].d, move S21openafs-client to S22openafs-client (or whatever numbers you need; I think I recall those were the ones). That change should be preserved through any upgrades of either software package. With the squeeze release, Debian will switch to dependency-based boot ordering, and you'll need to modify /etc/init.d/openafs-client. At the top, you'll want to add dnsmasq to the Required-Start line, which forces it to be started first. This change will be preserved on upgrades, but if the openafs-client init script changes, you'll have to merge this change with the new changes. I think there's also some way to use a separate override file in /etc/insserv/overrides so that you don't have to modify the script, but I don't know exactly how it works. You won't have to worry about that until squeeze, though. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
