All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Georgoulias <tom.georgoulias@freescale.com>
To: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: Please help - cleanup
Date: Thu, 06 May 2004 11:04:48 -0500	[thread overview]
Message-ID: <409A6220.80403@freescale.com> (raw)
In-Reply-To: <1083858912.5890.411.camel@d158140025182>

Chris Croswhite wrote:
> I ran this on 40 clients last evening through our normal regression runs
> (9 hours, 1.5T of data, 127 mount points) and found that it behaved as
> expected.

I should clarify, the mount dropping problem I mentioned in my last 
message is not specifically related to testing autofs-4.1.2-5 (or any 
4.1.2, I think).  I've got 4.1.1 rolled out and those systems are the 
ones dropping mounts, at least at this point in time.  My intention is 
to find a autofs release or set of patches that fixes this behavior 
sooner rather than later as it is causing problems for my users.

Just for my sanity, can anyone help me confirm the following "facts" 
about earlier behavior of the autofs-4.1.0pre10 release:

1.  NIS maps were not cached by the automounter daemon
2.  changes made to the maps and pushed out went into effect 
immediately, regardless of whether or not the changes were new key/mount 
entries to an existing map or just changes to existing key/mount pairs 
withing an existing map.

> I also think that it would be nice to have some form of
> regressions/tests to help validate.

I think it's time to start developing some.  Since Red Hat tests their 
software before they ship it, maybe they have a suite already in place 
that they could share? ;)

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

  reply	other threads:[~2004-05-06 16:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 14:13 Please help raven
2004-05-03 13:21 ` Jeff Moyer
2004-05-04 14:44 ` Please help - cleanup raven
2004-05-04 14:59   ` Jeff Moyer
2004-05-04 15:16     ` raven
2004-05-05 22:16       ` Jeff Moyer
2004-05-05 23:45         ` Michael Blandford
2004-05-06  1:38           ` Ian Kent
2004-05-06 12:40           ` Jeff Moyer
2004-05-06 14:44             ` raven
2004-05-06 14:30         ` Tom Georgoulias
2004-05-06 15:55           ` Chris Croswhite
2004-05-06 16:04             ` Tom Georgoulias [this message]
2004-05-06 19:10               ` Jeff Moyer
2004-05-06 19:34                 ` Peter C. Norton
2004-05-07 15:13                 ` Mike Waychison
2004-05-07  1:50               ` 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=409A6220.80403@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.