From: Frank Thommen <frank.thommen@embl.de>
To: hugo tempo <hugo@mx9.artware.nl>
Cc: autofs@linux.kernel.org
Subject: Re: different behaviour of autofs
Date: Fri, 01 Apr 2011 09:57:28 +0200 [thread overview]
Message-ID: <4D958568.2030904@embl.de> (raw)
In-Reply-To: <4D903E64.6050901@mx9.artware.nl>
hugo tempo wrote:
> Hi,
> We (@vu.nl) use the automounter with ldap, a.o. to automount
> home-directories.
> Now under squeeze if we do a wildcard access (ls /home/* or even ls
> /home) we get a listing of (seemingly) all the userdirectories from the
> mountmap (in ldap), which are certainly not all mounted under /home on
> that specific machine. Same story with /net where we automount packages.
> With lenny we never saw this behaviour, which we honestly do not
> appreciate.
> Anybody knowing the specifics about this?
> Thanks in advance,
> Hugo Bokman
Maybe the default of the browse mode has changed from "no" to "yes" from
the previous to the current Linux release ytou are using?
frank
prev parent reply other threads:[~2011-04-01 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 7:53 different behaviour of autofs hugo tempo
2011-04-01 4:14 ` Ian Kent
2011-04-01 7:57 ` Frank Thommen [this message]
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=4D958568.2030904@embl.de \
--to=frank.thommen@embl.de \
--cc=autofs@linux.kernel.org \
--cc=hugo@mx9.artware.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).