Re: named and nfs mounts at boot time

2007-07-24 Thread Christopher Sean Hilton
On Mon, 2007-07-16 at 09:12 -0500, Reid Linnemann wrote:
 Written by Tim Daneliuk on 07/13/07 17:29
  
  'Just wondering if there is a way to get the warnings during boot to
  be quiet without resorting to using IP addresses in the fstab nfs
  mount entries...
  
  

 If the filesystems are not needed until the system is up multiuser, you 
 could specify the 'late' option on them in fstab, forcing them to be 
 delayed until /etc/rc.d/mountlate is run after /etc/rc.d/DAEMON has 
 completed. This will ensure that named is running prior to the mount, 
 since DAEMON requires SERVERS, which starts named.

It seems like a lot of work but the automounting daemon amd solves these
and other issues with an nfs server being unavailable when an nfs client
boots up.

-- Chris

-- 
   __o  All I was doing was trying to get home from work.
 _`\,_   -Rosa Parks
___(*)/_(*)___
Christopher Sean Hiltonchris | at | vindaloo.com
 pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: named and nfs mounts at boot time

2007-07-16 Thread Reid Linnemann

Written by Tim Daneliuk on 07/13/07 17:29

While we're on the subject of dns ... I have nfs mounts configured in
/etc/fstab using the host *name*.  When the system boots, it grumbles
about the name resolution because named has not yet been started.  It
works fine because, by the time you have a fully booted system, named is
running and nfs runs happily.

'Just wondering if there is a way to get the warnings during boot to
be quiet without resorting to using IP addresses in the fstab nfs
mount entries...




If the filesystems are not needed until the system is up multiuser, you 
could specify the 'late' option on them in fstab, forcing them to be 
delayed until /etc/rc.d/mountlate is run after /etc/rc.d/DAEMON has 
completed. This will ensure that named is running prior to the mount, 
since DAEMON requires SERVERS, which starts named.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: named and nfs mounts at boot time

2007-07-13 Thread Chuck Swiger

On Jul 13, 2007, at 3:29 PM, Tim Daneliuk wrote:

While we're on the subject of dns ... I have nfs mounts configured in
/etc/fstab using the host *name*.  When the system boots, it grumbles
about the name resolution because named has not yet been started.  It
works fine because, by the time you have a fully booted system,  
named is

running and nfs runs happily.

'Just wondering if there is a way to get the warnings during boot to
be quiet without resorting to using IP addresses in the fstab nfs
mount entries...


Put the NFS server IPs and hostnames into /etc/hosts.

--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]