From: Christopher Slater <olyar@yahoo.com>
To: James Kelty <jamesk@everbase.net>,
linux-net@vger.kernel.org, linux-admin@vger.kernel.org
Subject: RE: amd or autofos?
Date: Tue, 16 Apr 2002 15:09:45 -0700 (PDT) [thread overview]
Message-ID: <a9i7fc$ark$2@main.gmane.org> (raw)
In-Reply-To: <MDEDIKPCLCIKDGEMDJGMKEMLCIAA.jamesk@everbase.net>
However, by hard mounting the NFS mount you will get stale mounts if
the server goes down.
I've had good luck with AMD, but I think you're right that autofs
seemed easier to configure.
I would guess that you should be able to fix the problem you're
currently seeing using *either* package. Could be unrelated to the
package, or a bug in the older version that might be installed.
Chris
--- James Kelty <jamesk@everbase.net> wrote:
> If you just want to mount the NFS shares at boot and keep them there,
> you
> can
> just edit the /etc/fstab file to reflect that.
>
> -James
>
> -----Original Message-----
> From: linux-admin-owner@vger.kernel.org
> [mailto:linux-admin-owner@vger.kernel.org]On Behalf Of Paul Furness
> Sent: Tuesday, April 16, 2002 5:59 AM
> To: linux-net@vger.kernel.org; linux-admin@vger.kernel.org
> Subject: amd or autofos?
>
>
> Hi, all.
>
> Is there someone around with lots of experience of auto mounting nfs
> shares on RedHat?
>
> Here's the setup:
> I have just taken over running the network and servers for this nice
> company, and we currently have a number of servers (all running
> RedHat
> 6.2) that variously run NIS, apache, various databases, and lots of
> disk
> space. The disks are shared using nfs shared, and then mounted using
> AMD
> on whichever machine the user logs in to. This includes not only
> shared
> volumes of data, but also the home directories of the users.
>
> There is an ongoing problem where AMD on a random machine dies at a
> random time, and has to be restarted so people can access files
> again.
>
> It is my intention to upgrade all the servers to RH7.2 (I could
> update
> the individual packages and the build a kernel, but a full upgrade
> seems
> a whole lot simpler to manage!) and I also have the chance to update
> how
> some of it works.
>
> So given an unrestricted choice between ams and autofs, which would
> you
> go for? Is autofs more stable than amd? It certainly looks to be
> slightly better documented and slightly easier to configure.
>
> Any thoughts would be appreciated.
>
> Thanks.
>
> BUNgle
>
> "One of these days I'll figure how the damn thing works..."
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
next parent reply other threads:[~2002-04-16 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MDEDIKPCLCIKDGEMDJGMKEMLCIAA.jamesk@everbase.net>
2002-04-16 22:09 ` Christopher Slater [this message]
[not found] <20020416220945.55540.qmail@web12806.mail.yahoo.com>
2002-04-17 11:23 ` amd or autofos? Paul Furness
2002-04-16 12:58 Paul Furness
2002-04-16 20:46 ` James Kelty
2002-04-16 20:48 ` James Kelty
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='a9i7fc$ark$2@main.gmane.org' \
--to=olyar@yahoo.com \
--cc=jamesk@everbase.net \
--cc=linux-admin@vger.kernel.org \
--cc=linux-net@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).