Andrew Deason <adea...@sinenomine.net> writes: > Adam Megacz <a...@megacz.com> wrote:
>> I've got my openafs cache in tmpfs (via a loopback-mount), so every >> time the machine comes up it sees an empty cache directory and spends >> some time "Starting AFS cache scan..." -- creating the directory >> structure. >> >> Unfortunately the AFS startup script returns before this process >> finishes. This means that other startup scripts -- which depend on >> /afs being mounted -- will end up running before /afs has been mounted. >> >> Is there any way to change this behavior so that >> /etc/init.d/openafs-client doesn't yield control until it has at least >> attempted to mount /afs? > Debian? > I don't think there's any init script options or anything to do that, > but if you want to edit the init script locally... > If you just run afsd directly instead of backgrounding it, it sounds > like it'll do what you want. That is, replace the line in the script > that has "start-stop-daemon --start <stuff> /foo/afsd -- $AFSD_OPTIONS" > with just "/foo/afsd $AFSD_OPTIONS". Is there any reason not to do this? If not, I can just make this change in the Debian package. I don't recall why start-stop-daemon was used there in the first place. -- Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/> _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
