Date: Mon, 4 Aug 2014 18:17:10 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@freebsd.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-current@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: [CFT] Autofs. Message-ID: <20140804161710.GA32801@pc5.home> In-Reply-To: <3DA39B51-4CE5-437B-9B03-7E34CC954A7E@lists.zabbadoz.net> References: <20140730071933.GA20122@pc5.home> <3DA39B51-4CE5-437B-9B03-7E34CC954A7E@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 0804T1252, Bjoern A. Zeeb wrote: > On 30 Jul 2014, at 07:19 , Edward Tomasz Napierała <trasz@freebsd.org> wrote: > > > At the link below you will find a patch that adds the new automounter. > > The patch is against yesterdays 11.0-CURRENT. > > > > http://people.freebsd.org/~trasz/autofs-head-20140729.diff > > I also just submitted https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192379 to allow -o vers= mount_nfs compatibility, which makes it easier to integrate with Linux/OSX/Solaris LDAP setups and mount options from LDAP. Nice! Will you commit it? > > Testing is welcome. Please start with manual pages, eg. automount(8). > > > I found one case now doing the aforementioned where when the initial mount_nfs fails (e.g., for invalid options), then a later mount did not succeed either, with the correct mount options; I did try to run automount -u in between tries, as well as service automountd restart, but that did not make a change; given I was short on time, a reboot of my desktop made this go away. Is there some “negative caching” in the kernel module possibly that will not retry the mount for another time or something—as in if I were more patient and waited 5 minutes, would it maybe just have worked again? There is no negative caching. I'll see if I can figure out the cause for this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140804161710.GA32801>