Path: utzoo!utgpu!watserv1!watmath!att!att!bu.edu!rpi!zaphod.mps.ohio-state.edu!ncar!gatech!mcnc!beguine!durham!robinson
From: robinson@durham.med.unc.edu (Gerard A. Robinson)
Newsgroups: comp.databases
Subject: Re: Ingres and NFS
Message-ID: <1474@beguine.UUCP>
Date: 30 Oct 90 03:23:24 GMT
References: <4691@spdcc.SPDCC.COM>
Sender: usenet@beguine.UUCP
Reply-To: robinson@uncmed.med.unc.edu (Gerard A. Robinson)
Organization: UNC-CH School of Medicine, Office of Information Systems
Lines: 23

In article <4691@spdcc.SPDCC.COM> dyer@ursa-major.spdcc.com (Steve Dyer) writes:
>
>I've heard that Ingres rel 6 "doesn't work" on NFS.  I'd like
>to get a better restatement or a refutation of the problem. 
>
The most likely answer to this is that INGRES version 6.0-6.2 had no
provisions for supporting diskless clients sharing an INGRES directory tree.
There was an internal document which one could obtain that described how to
cobble together an installation, which worked, but was tedious.  Version 6.3
(for Suns at least) provides an additional directory under II_SYSTEM, the
admin directory.  Under 'admin' there is a directory for each host sharing
the distribution.  This directory contains the files for global INGRES
environment variables and INGRES/Net startup options.  The installation
assumes (correctly) that no DBMS servers will be running.  This makes the
installation much easier.  While there are still no provisions for sharing
the INGRES/Net authorization and control files, it is much nicer than in
6.2.

Your supposition that an NFS mounted directory can be a valid area for 
database storage for a single installation, is correct, at least in
practice.  It is probably not a 'supported' configuration, however.

Gerard Robinson