>Date: Tue, 15 Feb 2000 12:40:21 +1100 (EST)
>From: Andy Farkas <[EMAIL PROTECTED]>
>Seems like a good idea to me not to have a message displayed if
>explicitly configured not to do something!
:-}
>If you have `nfs_enable_client="NO"' and if you have nfs mounts in your
>fstab, then this coul
On Mon, 14 Feb 2000, Doug Barton wrote:
> Far better is:
I knew I should have tested this first
# Mount NFS filesystems.
if mount -d -a -t nfs | grep nfs >/dev/null 2>&1 ; then
echo -n "Mounting NFS file systems"
mount -a -t nfs
echo .
fi
Doug
--
"Welcome t
On Mon, 14 Feb 2000, David Wolfskill wrote:
> I discovered this under 3.4-R, and checked that it's still the case
> for 4.0-RC.
FWIW, in my process of rewriting the rc* scripts I came across
quite a few of these extraneous messages/dependencies/etc. Improving this
situation is "on my lis
Seems like a good idea to me not to have a message displayed if
explicitly configured not to do something!
If you have `nfs_enable_client="NO"' and if you have nfs mounts in your
fstab, then this could be a method of delaying those mounts until after
boot/init time?
On Mon, 14 Feb 2000, Dav
Hi David,
On 14-Feb-00 David Wolfskill wrote:
> I discovered this under 3.4-R, and checked that it's still the case
> for 4.0-RC.
>
> I'm putting together a box that has no reason whatsoever to use or
> provide any NFS services at all.
>
> It was thus with a sense of "POLA violation" that I hap
