[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1822.0. "Pathworks 6.1 in a Unix Tru Cluster Environment" by NNTPD::"[email protected]" (Mark Sowards) Thu Apr 17 1997 21:16

  I need to know some details on how the setup for PathWorks works. 
Specificaly
what files are shared between the members of the cluster (i.e. the internal 
control and config files), where can I fine a description of these files, and
is
setting up Pathworks as a disk service the only way to get Pathworks
clustered?  
    Currently I have tried is using a AdvFS fileset as the device input
during the config script and then giving it the fully qualified mount point
that
the Tru-Cluster/ASE serves up as a service, but this cause the "pwsetup
config"
script to fail with a can't mount home#pwunix on /var/ase/.....  This
directory
is mounted and made available by the ASE service already defined.   
    The main problem is I can't set PathWorks up as a disk service.  It must
be 
a subpart to a Login/user defined service.  This service will provide to the 
users logging into it a home directory that is visible to Unix work Stations
and 
Mac Machines (using Helios) and Win 95/WinNT (using Pathworks).  There are no
more empty or unsued devices left on the shared bus, but file domain shared
out by the service has room.  I want to use this area for the common files 
that two pathworks installations (one on each ASE member) will share between 
themselves.  
   Has this been tried before?  Does anyone have any ideas on setting
pathworks 
up as a subpart to another service?
    
     

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
1822.1Here's someVIRGIN::SUTTERWho are you ??? - I'm BATMAN !!!Fri Apr 18 1997 06:2984
I've setup Pathworks V6.1A in a TruCluster environment recently.

Here are the files that are shared: 

# pwd
/usr/var/net/servers/lanman

ls -al
total 80
drwxrwxr-x  10 lanman   DOS----     8192 Apr  7 15:50 .
drwxrwxrwx   4 root     system      8192 Mar 25 14:41 ..
-rw-r--r--   1 root     DOS----        0 Mar 25 16:05 .LCK.ctrl
-rw-r--r--   1 root     DOS----        0 Mar 25 16:06 .LCK.repl
prw-rw----   1 root     DOS----        0 Apr  7 15:50 .ctrlpipe
drwxrwxr-x   2 lanman   DOS----     8192 Mar 25 14:34 bin
drwxrwxr-x   2 lmxadmin DOS----     8192 Mar 25 14:34 cat
drwxrwxr-x   2 lanman   DOS----     8192 Mar 25 14:42 clipr
drwxr-xr-x   2 lanman   DOS----     8192 Mar 25 14:34 customs
drwxrwxr-x   3 lanman   DOS----     8192 Mar 25 14:43 datafiles
lrwxrwxrwx   1 root     DOS----       33 Mar 25 14:42 debug -> /pwk/usr/net/serv
ers/lanman/debug
lrwxrwxrwx   1 root     DOS----       35 Mar 25 14:43 domains -> /pwk/usr/net/se
rvers/lanman/domains
lrwxrwxrwx   1 root     DOS----       38 Mar 25 14:43 lanman.ini -> /pwk/usr/net
/servers/lanman/lanman.ini
lrwxrwxrwx   1 root     DOS----       32 Mar 25 14:42 logs -> /pwk/usr/net/serve
rs/lanman/logs
drwxrwxrwx   4 lanman   DOS----     8192 Apr  7 18:07 mailslot
drwxr-xr-x   2 root     system      8192 Mar 25 14:34 scripts
drwxrwxr-x   2 lanman   DOS----     8192 Mar 25 14:34 service
lrwxrwxrwx   1 root     DOS----       37 Mar 25 14:43 sharefile -> /pwk/usr/net/
servers/lanman/sharefile
lrwxrwxrwx   1 root     DOS----       11 Mar 25 17:49 shares -> /pwk/shares
lrwxrwxrwx   1 root     DOS----       33 Mar 25 14:43 spool -> /pwk/usr/net/serv
ers/lanman/spool
lrwxrwxrwx   1 root     DOS----       31 Mar 25 14:43 tmp -> /pwk/usr/net/server
s/lanman/tmp

# pwd
/usr/var/net/servers/pathworks
# ls -al
total 35
drwxrwxrwx   4 root     system      8192 Mar 25 14:41 .
drwxr-xr-x   3 root     system      8192 Mar 11 12:18 ..
drwxrwxr-x  10 lanman   DOS----     8192 Apr  7 15:50 lanman
drwxrwxr-x   7 root     system      8192 Apr  7 15:50 pathworks
-rwxr-xr-x   1 lp       other       2609 Mar 25 14:41 prntfault
swissair:/usr/net/servers # cd pathworks
swissair:/usr/net/servers/pathworks # ls -al
total 57
drwxrwxr-x   7 root     system      8192 Apr  7 15:50 .
drwxrwxrwx   4 root     system      8192 Mar 25 14:41 ..
-rw-r--r--   1 root     system         0 Mar 25 14:30 .LCK.lr
-rw-r--r--   1 root     system         0 Apr  7 15:50 .LCK.ls
-rw-r--r--   1 root     system         0 Mar 25 18:08 .LCK.lsapi
prw-rw----   1 root     system         0 Apr  7 15:50 .lr.conn
prw-rw----   1 root     system         0 Apr  7 15:50 .lr.disc
prw-rw----   1 root     other          0 Apr  7 15:50 .ls.api
prw-rw----   1 root     other          0 Apr  7 15:50 .ls.grp
drwxrwxr-x   2 root     system      8192 Mar 25 14:30 bin
drwxrwxr-x   2 root     system      8192 Mar 25 14:30 cat
lrwxrwxrwx   1 root     system        35 Mar 25 14:41 data -> /pwk/usr/net/serve
rs/pathworks/data
drwxrwxr-x   2 root     system      8192 Mar 25 14:41 datafiles
lrwxrwxrwx   1 root     system        35 Mar 25 14:41 logs -> /pwk/usr/net/serve
rs/pathworks/logs
-rw-r--r--   1 lanman   DOS----      156 Mar 25 14:43 pathworks.ini
drwxr-xr-x   2 root     bin         8192 Mar 25 14:30 relnotes
drwxrwxr-x   2 root     system      8192 Mar 25 14:43 scripts

I've my shared storage mounted on /pwk and did my installations according to
the TruCluster / Pathworks manual. 

I've had some problems with specifying AdvFS as the shared filesystem and 
configuring the USERS share on the shared storage area. This resulted
in QAR#1007 and QAR#1008 respectively. 

I've setup the PW service as a disk service with an IP address. Make sure
"service name == PW listen name == IP alias name". Your clients can then
connect to that service. 

Regards, 

Arnold
1822.2Thanks for the inputNNTPD::"[email protected]"Mark SowardsMon Apr 21 1997 11:1524
Thanks for your input.  
   Here I want to followup on what Jim Lola and I have done with this.  
Since Jim's design of this TruCluster had no free disk device to give to 
Pathworks we decided to continue the style of TruCluster that Jim has started.
He created a cross bread (let's say a 5th type of) service.  This service has
its own IP address, is a NFS service, application service and a disk service 
combined.  One of the services it offeres is a hugh AdvFS file domain from
this 
domain Jim has created multiple fileSets.  As you know a AdvFS fileSets can be

treated almost like a disk device.  So therefore, it should have worked with
the
Pathworks TruCluster config/installation script; however, in several locations
through out the script the type of file system assumed to be in use with 
the Pathworks member shared disk is UFS.  we editted the scripts and forced
the 
FS type to AdvFS.  We were able to complete the installation successfully. 
Jim 
has also successfully Clustered Helios a replacement for the Appletalk product
that was lost due to a corporate take over of a third party.  Helios seems to
be
compatable with Pathworks.  Testing will continue in the weeks to come.  
 
[Posted by WWW Notes gateway]