All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Odd NIS map failure with mount point creation time in the future?
Date: Mon, 20 Jun 2011 11:45:59 +0100	[thread overview]
Message-ID: <4DFF24E7.4020407@moving-picture.com> (raw)
In-Reply-To: <1308453488.3300.3.camel@perseus.themaw.net>

Ian Kent wrote:
> 
> That sounds a bit like bug
> https://bugzilla.redhat.com/show_bug.cgi?id=632471

I don't have permission to view that bug ...

> It was fixed in development revision 152, which I happen to have on
> people.redhat.com. You could give that a try.
> 
> http://people.redhat.com/~ikent/autofs-5.0.1-0.rc2.152.el5/

Unfortunately, this version doesn't help ...

Thanks

James Pearson

  reply	other threads:[~2011-06-20 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 14:12 Odd NIS map failure with mount point creation time in the future? James Pearson
2011-06-18 10:18 ` Ian Kent
2011-06-18 15:59   ` James Pearson
     [not found]     ` <4DFD05CE.4060905@moving-picture.com>
2011-06-19  3:18       ` Ian Kent
2011-06-20 10:45         ` James Pearson [this message]
2011-06-20 13:40           ` 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=4DFF24E7.4020407@moving-picture.com \
    --to=james-p@moving-picture.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.