All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Daniel Qarras <dqarras@yahoo.com>
Cc: autofs@linux.kernel.org
Subject: Re: AutoFS Problems with Laptops
Date: Mon, 22 May 2006 16:07:15 +0800	[thread overview]
Message-ID: <44717133.3000304@themaw.net> (raw)
In-Reply-To: <20060522075327.23988.qmail@web36807.mail.mud.yahoo.com>

Daniel Qarras wrote:
> Hi Ian,
> 
> and thanks for your prompt reply.
> 
>>> I am asking this because I've tried almost everything and I am just
>>> getting bizarre results like directory /var/autofs/(null)/home,
>> -------------------------------------------------------^
>> You'd be running FC5 then.
>> Can't track this down, we shouldn't be getting mount requests from
>> the kernel with no name.
> 
> Yes, the client is FC5, the server is CentOS-4.4. At the server only
> /etc/exports is configured like this:
> 
> /home           10.0.0.0/255.0.0.0(rw,no_root_squash,sync)
> /work           10.0.0.0/255.0.0.0(rw,no_root_squash,sync)
> 
>> A script should just output the map entry without the key. Like
>> -fstype=nfs,rw,soft,intr 10.0.0.1:/work
> 
> Unfortunately, this still creates (null) directory and I can even go to
> /var/autofs/whatever to see contents of /work. And if the script
> outputs both /work and /home I see only either of them, depending the
> order the entries are printed and if they are on the same line or in
> two lines.

That's interesting.

You mean you get a directory "(null)" with no mount?
That shouldn't happen because the the "(null)" key shouldn't be found 
and so shouldn't have a mount entry associated with it. If the script 
needs to return a fail on the lookup it should return 1, 0 on success.

If the script emits a valid mount then it will, of course, mount that.

Ian

  reply	other threads:[~2006-05-22  8:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  8:17 AutoFS Problems with Laptops Daniel Qarras
2006-05-19 13:36 ` Ian Kent
2006-05-22  7:53   ` Daniel Qarras
2006-05-22  8:07     ` Ian Kent [this message]
2006-05-22  9:11       ` Daniel Qarras
2006-05-22 10:45         ` Ian Kent
2006-05-22 11:51           ` Daniel Qarras
2006-05-20 23:34 ` Jim Carter
     [not found] <4471DDEF.8050203@themaw.net>
2006-05-23  7:43 ` Daniel Qarras

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=44717133.3000304@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=dqarras@yahoo.com \
    /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.