All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Georgoulias <tom.georgoulias@freescale.com>
Cc: autofs@linux.kernel.org
Subject: Re: Severe problem with 4.1.2: automount caches NIS maps forever
Date: Thu, 06 May 2004 16:07:55 -0500	[thread overview]
Message-ID: <409AA92B.8050104@freescale.com> (raw)
In-Reply-To: <200405061811.i46IBbbv019272@miguelito.qualcomm.com>

mmarion@qualcomm.com wrote:
> On  6 May, Bryan O'Sullivan wrote:
>>The autofs 4.1.2 release has a change in behaviour from earlier releases
>>(4.1.0, I think, and 4.0.0 for sure) in that it never checks to see if a
>>NIS-based automount map has changed.

> I noticed this too and did a workaround...

Why was the behavor changed between releases?  I was asking about this 
in my other message and now I see that two other people can confirm the 
need to HUP for daemons to use new map changes.

Tom
-- 
Tom Georgoulias
POPI Classification
[x] General Business Information
[] Freescale Semiconductor Internal Use
[] Freescale Semiconductor Confidential Proprietary

  reply	other threads:[~2004-05-06 21:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 17:39 Severe problem with 4.1.2: automount caches NIS maps forever Bryan O'Sullivan
2004-05-06 18:11 ` mmarion
2004-05-06 21:07   ` Tom Georgoulias [this message]
2004-05-06 21:22 ` Michael Blandford
2004-05-07  2:10   ` Ian Kent
2004-05-07  3:45     ` Jim Carter
2004-05-07  4:23       ` Ian Kent
2004-05-07 18:45       ` Michael Blandford
2004-05-08  5:20         ` raven
2004-05-09  6:11           ` Jim Carter
2004-05-07 17:58     ` Bryan O'Sullivan
2004-05-08  5:44       ` raven
2004-05-08 21:26         ` Bryan O'Sullivan
2004-05-09  3:59           ` raven

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=409AA92B.8050104@freescale.com \
    --to=tom.georgoulias@freescale.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.