Robert Joosten wrote: > Someone pointed out to disable rpc.lockd completely but that doesn't help > either. Unless the pxe-clients have to do something on their end I'm not > aware of. > > Another stated rpc.lockd is broken for years now and we should > implement a dummy one accepting and positively ack all locks while > doing nothing actually. That should work as long as you know what you're > doing :-D My pxe clients all have separate directories so concurrent locks > on one specific file shouldn't occur.
In that case you can savely mount with the -L option (a.k.a. "-o nolockd"), an everything will just work. No need for rpc.lockd at all. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll." -- Frank Klemm, de.comp.os.unix.discussion _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
