[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NFS mounting with cfengine
From: |
Doug Chapman |
Subject: |
Re: NFS mounting with cfengine |
Date: |
Mon, 8 Aug 2005 20:47:22 -0700 |
Highly recommend using automount. You get the advantage of timing out
inactive mount points and if you use wildcards you may not have to
update this file very often.
Here's a sample of what we're doing (you'll need to also add a row to
/etc/auto.master)
editfiles:
linux::
{ /etc/auto.remote
BeginGroupIfNoLineMatching '#auto.remote managed by cfengine v 1.9'
Backup "off"
EmptyEntireFilePlease
Append '#auto.remote managed by cfengine v 1.9'
Append '* -rw,timeo=600,hard,intr,bg nas01:/vol/&'
EndGroup
DefineClasses "reloadautofs"
}
shellcommands:
last.reloadautofs::
"/sbin/service autofs reload"
On 8/8/05, Frank Smith <fsmith@hoovers.com> wrote:
> --On Monday, August 08, 2005 13:00:19 -0400 Jeremy Dreese
> <jdreese@bucknell.edu> wrote:
>
> >
> >> So the question is should I simply do that with a static entry in fstab
> >> and forget about using cfengine for the mounting itself? Or do I really
> >> missunderstand the concept of NFS mounts with cfengine?
> >
> > You can use "miscmounts" to mount these directories. I think something
> > like this should work:
> >
> > miscmounts:
> >
> > SystemGroup::
> >
> > blender:/vol/apps /usr/appdir mode=tcp
>
> Be aware that cfengine's mount code isn't very bright. It generates
> a line for the [v]fstab based on some defauults and the options
> you specify, and if it isn't already there it will add it to the file
> and try to mount it. Sounds good in theory, but it checks for an
> exact match in the file and doesn't check to see if it is already
> mounted, so you can easily end up with double mounts. even if it is
> only a difference in whitespace. This can cause problems on some
> systems.
> Also, even if you use cfengine for the initial mount (i.e., aren't
> trying to convert existing manual mounts to cfengine control), you
> can't modify the mounts or the mount options, since there is no
> practical way to unmount or remount a filesystem. You can't even
> make the fstab changes and wait for the next reboot, since cfengine
> will try to mount everything in it every time it runs.
>
> Frank
>
> >
> >
> > --
> > Jeremy Dreese
> > Engineering Computing Systems Integrator
> > College of Engineering
> > Bucknell University
> > voice: (570) 577-3714
> > fax: (570) 577-3579
> > email: jdreese@bucknell.edu
> >
>
> --
> Frank Smith fsmith@hoovers.com
> Sr. Systems Administrator Voice: 512-374-4673
> Hoover's Online Fax: 512-374-4501
>
>
>
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine
>
--
Doug Chapman
Revenue Science