home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!europa.eng.gtefsd.com!paladin.american.edu!auvm!INNOSOFT.COM!DAN
- Errors-to: epmdf@YMIR.BITNET
- X-Envelope-to: PMDF-L@IRLEARN.BITNET
- X-VMS-To: IN%"JLW%PSULIAS.BITNET@YMIR.CLAREMONT.EDU""J.Lance Wilkinson,
- 814-865-1818"
- X-VMS-Cc: IN%"ipmdf@INNOSOFT.COM"
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GU0IIZYWS28WVZMJ@INNOSOFT.COM>
- Date: Wed, 27 Jan 93 21:25:56 GMT
- Sender: PMDF Distribution List <PMDF-L@IRLEARN.BITNET>
- From: "Daniel C. Newman" <dan@INNOSOFT.COM>
- Subject: RE: My most common installation question....
- Newsgroups: bit.listserv.pmdf-l
- In-Reply-To: Your message dated "Wed,
- 27 Jan 1993 14:18 -0500 (EST)"
- <01GU0LKKVLG0CRHC52@psulias.bitnet>
- Lines: 55
-
- >I swear I ask somebody this question every time I install PMDF. What's the
- >answer this release (v4.1)?
- >
- > I have a completely homogenous cluster, per the definition on page 1-4
- > of the v4.1 Installation guide, first paragraph in section 1.3.2.
- >
- > Can I simply do *one* VMSINSTAL run, on the primary member of the
- > cluster, or must I run VMSINTAL on that primary member (a VAX9420),
- > then do the same thing all over again on our VAX6420, our VAXStation
- > 3100, and all eleven of our VAXStation 4000 VLC's?
-
- Yes, just do one install on one machine for the entire cluster. This will
- give you one PMDF directory tree. You can install on top of the existing
- PMDF directory tree or start another one.
-
-
- If you start another one then you have to copy the queue subdirectories and
- their contents from pmdf_root:[queue...] as well as the configuration files
- from the old table directory. After copying over the queue subdirectories
- (and contents), run PMDF_ROOT:[EXE]SYNCH_CACHE to synchronize the queue
- cache database.
-
- > I know I'll still have to stop PMDF and all other network mail
- > operations on all cluster members, then reinstall/restart using
- > SYS$STARTUP:PMDF_STARTUP.COM on each cluster member, after the
- > VMSINTAL and post-installation tasks. I'm not worried about that;
- > I just think it's silly and a significant waste of time to run
- > VMSINTAL 14 times with the same results each time -- or *are* they
- > really the same results each time (construction of the PMDF_ROOT:[...]
- > directory tree)?
-
- There was no need to run it more than once.
-
- > If I sound really dense on this, I'll quote from, again, page 1-4
- > of the Installation guide, first paragraph in section 1.3.2:
- >
- > "If you have a completely homogenous VAXcluster, ...,
- > installing PMDF is essentially the same as on a single
- > node. All individual host names are essentially aliases
- > for a single host, and should be rewritten to the local
- > host name."
- >
- > It *sounds* to me like all I need to do is *one* VMSINTAL, followed
- > by taking care to include all my post-installation tasks (running
- > CONFIGURE, editing PMDF.CNF, etc.). But given that JNET needs to
- > be VMSINTAL'd on every node, and I clearly remember doing the same
- > for PMDF back when we only had the 9420 and 6420 (as well as PMDF
- > v3.1), I don't want to make the mistake, while doing this in the
- middle
- > of the night on a weekend when nobody @innosoft is able to answer
- > the phones and I have myself screwed....;-{
-
- Unlike Jnet, once for the entire cluster is enough for PMDF.
-
- Dan
-