From: Greg Bradner <gregb@rhythm.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: [ANNOUNCE] autofs v4 beta3 (fwd)
Date: Thu, 13 Nov 2003 06:39:53 -0800 [thread overview]
Message-ID: <3FB397B9.9010600@rhythm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0311131542180.11228-100000@wombat.indigo.net.au>
I have multiple mount points on a NetApp, but I don't have 'access'
permissions to all of them. When autofs encountered a permission denied
on one of the mount points, it didn't mount any of them. Shouldn't it
just skip over the permission denied one and still mount the others?
Nov 11 15:13:32 lid2 automount[2454]: attempting to mount entry
/nfs/hosts3/rosie
Nov 11 15:13:32 lid2 automount[18879]: >> mount: rosie:/vol/vol0/reserve
failed, reason given
by server: Permission denied
Nov 11 15:13:32 lid2 automount[18879]: mount(nfs): nfs: mount failure
rosie:/vol/vol0/reserve
on /nfs/hosts3/rosie/vol/vol0/reserve
Nov 11 15:13:32 lid2 automount[2454]: attempting to mount entry
/nfs/hosts3/rosie
Nov 11 15:13:32 lid2 automount[18883]: >> mount: rosie:/vol/vol0/reserve
failed, reason given
by server: Permission denied
Ian Kent wrote:
>---------- Forwarded message ----------
>Date: 11 Nov 2003 20:51:57 +0800
>From: Ian Kent <raven@themaw.net>
>To: autofs@linux.kernel.org
>Subject: [ANNOUNCE] autofs v4 beta3
>
>
>Status
>------
>
>I'm hoping that this will be the last beta of 4.1.0.
>
>I expect to release 4.1.0 final and corresponding kernel module kit
>within
>a week or so.
>
>The only bug reports I have had relate to multi-mount problems and this
>beta includes updates for them as far as they can be fixed at this
>stage. This leaves one outstanding problem with multi-mount maps. The
>senario is that the daemon cannot remount a manualy umounted multi-mount
>entry until after the following expire event. This is due kernel module
>and daemon not knowing the umount has occured and consequently not
>cleaning up afterward. This causes the kernel module to return a longer
>path than it should which cannot be matched in the map. I hope to be
>able
>to fix this a some time in the future. In the mean time it is necessary
>to
>let the daemon do its thing and all should be OK.
>
>A reported problem with the documentation regarding the mailing list
>subscription instructions is also not yet corrected. Sorry, I'll get it
>done by the time of the final release.
>
>Packages
>--------
>
>As usual the packages can be found at:
>
>ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4
>
>They are:
>
>autofs-4.1.0-beta3.tar.[bz2|gz]
>autofs4-2.4-module-20031109.tar.[bz2|gz]
>
>Additionally there is an autofs-4.1.0-beta3.src.rpm. This has been
>included because the rpmbuild -tb command will not work properly on
>the tar with this release. Please don't try as the spec file in the tar
>is
>out of date. Use the src rpm instead.
>
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rhythm & Hues
5404 Jandy Place
Los Angeles, CA 90066
Voice: 310 448-7763
Fax: 310 448-7600
gregb@rhythm.com
next prev parent reply other threads:[~2003-11-13 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 7:43 [ANNOUNCE] autofs v4 beta3 (fwd) Ian Kent
2003-11-13 14:39 ` Greg Bradner [this message]
2003-11-13 15:52 ` Greg Bradner
2003-11-14 0:26 ` Ian Kent
2003-11-13 17:16 ` Taylor, ForrestX
2003-11-13 17:42 ` Greg Bradner
2003-11-13 17:57 ` Greg Bradner
2003-11-13 19:27 ` Taylor, ForrestX
2003-11-14 2:59 ` Ian Kent
2003-11-14 0:24 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FB397B9.9010600@rhythm.com \
--to=gregb@rhythm.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.