Digital Unix managers,
I have an mx records for client systems pointing to the following machine:
uhhepj
DEC 3000/300
DUNIX V2.0 240
nfslocking is on (set to 1)
nfs serves /var/spool/mail to clients
This setup has been working well for us.
However, uhhepj will be changed to a client system which means all
of the services that it provides has to move to another system.
My first step was to move /var/spool/mail to a filesystem of it own and move
the disk to the new nfsserver of the mail partition (changing the mx record
would be done after this first step was sucessful).
System B (new nfs server of /var/spool/mail):
fstab entry: /dev/rz2g /var/spool/mail ufs rw 1 2
exports entry: /var/spool/mail -root=0 list of client nodes...
AlphaStation 200 4/166
DUNIX V3.2 214
nfslocking is on (set to 1)
Turned on MAILLOCKING 0 --- according to man pages this specifies lockf
4 also specifies lockf, what is the
difference?
Results:
I can see all my mail in my INBOX (via pine), however,
I could not receive mail sent to myself locally nor mail sent to
myself via uhhepj. I found the following error message on uhhepj:
Feb 19 12:58:06 uhhepj binmail[564]: cannot lockf /usr/spool/mail/diane
I had to revert back to the original setup with System A nfsserving
/var/spool/mail and remove the MAILLOCKING 0 in rc.config for System B.
Question:
Why didn't this work? Is it a problem due to conflicts in handling
the locks between different versions of DUNIX?
Thank you
Diane Ibaraki
University of Hawaii
High Energy Physics Group
<diane_at_uhhepj.phys.hawaii.edu>
Received on Tue Feb 20 1996 - 19:28:17 NZDT