🚀 go-pugleaf

In article <5604@rosie.NeXT.COM> amm@NeXT.COM (Alan M. Marcum) writes:
>Marcel Waldvogel writes
>> We were trying the obvious: putting a /mounts entry in the / NetInfo
>> domain (name=server:/LocalApps, dir=/LocalApps). This works well on
>> all clients, but the server can't restart properly
>
>This sort of mount causes all pre-3.0 systems to hang when the
>mount is encountered.  In 3.0, this sort of mount is simply
>ignored.
>
>The classic pre-3.0 workaround is to rename the directory on the
>server, and mount server:/localapps on /LocalApps.  But, because
>of an old and very tricky NFS bug, writing on the server into
>/LocalApps in this situation might cause the server to hang.
>
>Best solution: upgrade to 3.0.
>--
>Alan M. Marcum
>NeXT Tech Support
>amm@NeXT.COM

Another solution:
Abort the mount if the directory existists. This can be done with
netinfomanager:

name:      server:/dir
dir:       /dir
opts:      rw
	   bg                    <---------------Background !!!
type:      nfs
passno:    0
freq:      0


This works for us with two servers mounting some directories across
and 6 clients.

---
Thomas Sporer                          Tel.  +49 9131 857201
Lehrstuhl Technische Elektronik        Fax.  +49 9131 302951
Cauerstr 9                             Email spo@lte.e-technik.uni-erlangen.de
W 8520 Erlangen