set the default mount options for the NFS filesystem(on the client) to
be soft(I believe default is hard). When the system boots if it cannot
mount it, it should continue, then when something tries to access it,
it will try(again) to mount it.
I am not really knowledgeable on that subject,
My users server does an NFS mounts of /var/mail from another system. If
for some reason all servers happen to get restarted (power failure comes to
mind), the mail spool server takes longer to boot up than the users one.
Consequently /var/mail never get mounted until I manually try to re-run
.
-Original Message-
From: Ashley M. Kirchner
To: Red Hat Mailing List
Sent: 12/2/02 12:34 PM
Subject: Relying on NFS availability
My users server does an NFS mounts of /var/mail from another system.
If
for some reason all servers happen to get restarted (power failure comes
to
mind), the mail
Ira Childress wrote:
See the man pages on automount and autofs. File systems can be setup to
mount only when accessed or needed. Automount systems typically don't mount
the file system until it is actually needed and then umount it after some
length of inactivity (10 minutes on Solaris).
On Mon, Dec 02, 2002 at 11:34:57AM -0700, Ashley M. Kirchner wrote:
Is there some way of checking whether an NFS mount is actually mounted for some
time after a system boots up?
Here's a short extract from our backup procedure. The intent of this is
to make sure that our backup mount point
Ashley M. Kirchner said:
Does something like this already exist? Is there some other solution
if
this isn't the proper way of doing it? Ideally I'd like to delay
sendmail's startup as well otherwise incoming mail will get stored on the
physical (local) /var/mail and when the NFS mount
