All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Heinrichs <ext-dirk.heinrichs@nokia.com>
To: autofs@linux.kernel.org
Subject: Re: Program maps - examples?
Date: Tue, 18 Nov 2003 15:31:31 +0100	[thread overview]
Message-ID: <3FBA2D43.9030609@nokia.com> (raw)
In-Reply-To: <B9F4645CD7B0D511BE8300508B68C327025EADB0@tnscapp02.pcacorp.net>

Stuckless, Colin wrote:
>  > Hello,

>  > Local:        /level1/level2/home/username
>  > Server: /prefix/homestore_[:a-z:]/username
 >  >
>  > This means when I want to mount my own home I have to mount
>  > server:/prefix/homestore_d/dheinric to /level1/level2/home/dheinric. I
>  > guess there's no other way than using a program map, but there's not
>  > much documentation/examples about this in the package. Can
>  > someone sched
>  > some light on this, please.
> 
> You can create an auto.home map on the server which has all the
> pathnames and mount points. For example, your auto_master would
> say:
> 
> /level1/level2/home auto_home
> 
> and then your auto_home map would have entries like:
> 
> dheinric server:/prefix/homestore_d/&
Tried this, but did not quite succeed. The problem is that this would 
require entries for every single user. But the following auto.home then 
worked for me:

#!/bin/bash
FIRST_LETTER=`echo $1|cut -c 1`
echo server:/prefix/homestore_${FIRST_LETTER}/$1

This returns the correct path.

> This would result in the client automounting /level1/level2/home/dheinric
> from server:/prefix/homestore_d/dheinric when you cd'd into the directory.
> 
>  
>  > I've also looked onto our Solaris machines. They seem to cascade the
>  > maps, which I guess is not possible on linux, right?
> 
> 
> I'm not sure what you mean by cascade, but their is a syntax I've
> seen referred to as 'multimount' where you have multiple subdirectories
> undr a single mount point, each seperated by a "\" continuation character.
> These exist on HP-UX and Solaris. The newest autofs does support this,
> I'm using the autofs-4.1 beta with these type of maps and it's working
> fine.
In auto_master they have a line "/level1 auto_level1", then in 
auto_level1, there is "level2 -fstype=autofs auto_level2", this is what 
I mean with cascading. Meanwhile, I found another Linux box here which 
does the same, but the syntax is different: "level2 -fstype=autofs 
file:/full/path/to/map"

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)151 1513 6954
Configuration Manager   | Fax:  +49 (0)211 47068 111
Cap Gemini Ernst & Young| Mail: dirk.heinrichs@cgey.com
Hambornerstraße 55      | Web:  http://www.cgey.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

       reply	other threads:[~2003-11-18 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B9F4645CD7B0D511BE8300508B68C327025EADB0@tnscapp02.pcacorp.net>
2003-11-18 14:31 ` Dirk Heinrichs [this message]
2003-11-18 12:55 Program maps - examples? Dirk Heinrichs

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=3FBA2D43.9030609@nokia.com \
    --to=ext-dirk.heinrichs@nokia.com \
    --cc=autofs@linux.kernel.org \
    /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.