Having it die earlier with a reasonable message if /afs doesn't exist would certainly solve the problem. If I get the chance I'll submit a patch to that affect (first I need to update my source).
-derek Nathan Neulinger <[EMAIL PROTECTED]> writes: > Cees de Groot wrote: > > > > Mike Lee <[EMAIL PROTECTED]> said: > > ><12>start afsd and get: > > >afsd: All AFS daemons startd > > >afsd: Can't mount AFS on /afs(22) > > > > > Step <11.5>: mkdir /afs > > > Just a thought - afsd is doing so much else at startup, why don't we put > in a mkdir if it's doesn't exist? Not that it matters for sites > following install instructions, but it's one less possible error > condition that new installers could encounter... > > Or for that matter - have afsd exit cleanly before it does anything > non-reversible, if /afs doesn't exist as a directory, and have it > generate a reasonable warning message. > > -- Nathan > > ------------------------------------------------------------ > Nathan Neulinger EMail: [EMAIL PROTECTED] > University of Missouri - Rolla Phone: (573) 341-4841 > Computing Services Fax: (573) 341-4216 > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
