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 09:30:28 -0500 [thread overview]
Message-ID: <409A4C04.1060604@freescale.com> (raw)
In-Reply-To: <16537.26586.135188.997029@segfault.boston.redhat.com>
Jeff Moyer wrote:
> Has anyone had the chance to test this? autofs-4.1.2-5 from my people
> page, or the patch Ian sent to the list? I'd like to hear feedback, either
> positive or negative as I have to push a package into FC2 before the
> freeze on Friday.
I have a system running it right now and it's behaving as expected, but
I haven't done any in depth testing of it because of other priorities.
What would be nice is to have a suite of smoke tests that I could run
through. Sometimes I don't see problems with new patches until much
later, after I thought I had wrung it out pretty well. ;)
The bigger problem I'm facing right now is mounts dropping and not
remounting until a HUP signal is sent to the daemon. I've hacked around
this by setting up a cron job to send the HUP on an hourly basis, but
this is far from an elegant solution.
Tom
--
Tom Georgoulias
POPI Classification
[x] General Business Information
[] Freescale Semiconductor Internal Use
[] Freescale Semiconductor Confidential Proprietary
next prev parent reply other threads:[~2004-05-06 14:30 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 [this message]
2004-05-06 15:55 ` Chris Croswhite
2004-05-06 16:04 ` Tom Georgoulias
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=409A4C04.1060604@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.