All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Swan <rswanster@gmail.com>
To: "raven@themaw.net" <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Re: debug failed automount
Date: Sun, 1 May 2005 19:18:21 -0400	[thread overview]
Message-ID: <1110130205050116184381a11e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0505012144150.2824@donald.themaw.net>

On 5/1/05, raven@themaw.net <raven@themaw.net> wrote:
> On Sat, 30 Apr 2005 raven@themaw.net wrote:
> 
> My response was a bit hasty I think.
> 
> > On Sat, 30 Apr 2005, Robert Swan wrote:
> >
> >> >
> >> >  One point is that the remote host is accessed through a VPN tunnel.
> >>
> >>  so as it turns out, this is the problem. The rpc_time call fails (I
> >>  assume this is because it is not supported by the VPN) and this marks
> >>  my only host as dead and automount does not attempt to mount. Even
> >>  though the mount actually works fine.
> >
> > Why? The rpc_ping connects to port 2049 on the target host.
> 
> You may be seeing a bug with the autofs mount code not trying a longer
> timeout if it fails to get a response in time.

I'm a bit confused myself because I can no longer replicate my
problem. I had made a test program to call your get_best_mount() with
my particular arguments so I could step through it, and  I'm _sure_
(aren't we all) that it would get a failed status from rpc_time at
line 238 and so would not assign a winner. I changed initial
assignment of "winner" at the start of the function which solved my
problem. I didn't look inside rpc_time to see what was going wrong; I
tried to do that today and now the status from rpc_time() is
successful, and your original code performs the mounts. So I don't
have a bug report and you can ignore me.

Is there a way to attach a debugger to the automount process that gets
spawned when the kernel attempts an automount?

Thanks anyhow for answering.

Robert

> 

> > _______________________________________________
> > autofs mailing list
> > autofs@linux.kernel.org
> > http://linux.kernel.org/mailman/listinfo/autofs
> >
> 
>

  reply	other threads:[~2005-05-01 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 14:19 debug failed automount Robert Swan
2005-04-30  5:27 ` Robert Swan
2005-04-30 15:27   ` raven
2005-05-01 13:46     ` raven
2005-05-01 23:18       ` Robert Swan [this message]
2005-05-02  2:03         ` Ian Kent
2005-05-02  2:52           ` Robert Swan
2005-05-02 13:54             ` raven
2005-05-06  4:19           ` Steven Ihde

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=1110130205050116184381a11e@mail.gmail.com \
    --to=rswanster@gmail.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.