[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

nlockmgr and /var/mail over NFS



Hi everyone,

sorry for the cross-post, but this could be a tru64 question as well as
an OBSD one.

I'm planning to use an i386 running OpenBSD 2.9 as our mailserver. All
our other boxes are running either Tru64 (various 5 versions) or 
(arrghh!) RH Linux 6.2. 

The setup I'd like to have is to export /var/mail on the obsd box to all
the other clients, but in my tests it seems I'm running into locking 
problems with the mail folders. I'm testing mutt, pine and mh as mail
clients (that's what my users use): on linux clients they all work, with
the lockd complaining about receiving garbage. On tru64 clients only mh
works and only if /var/mail is chmod 1777. It doesn't if /var/mail is
755. Pine and mutt are stuck waiting for the lock. 

In both cases (linux and tru64) a run of ethereal shows the openbsd box
complaining about nlockmgr v4 not being supported. Indeed, on the OpenBSD
box:

r2d2:~> rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100007    2   udp    896  ypbind
    100007    2   tcp    971  ypbind
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100001    1   udp    729  rstatd
    100001    2   udp    729  rstatd
    100001    3   udp    729  rstatd
    100002    1   udp    766  rusersd
    100002    2   udp    766  rusersd
    100002    3   udp    766  rusersd
    100005    1   udp    857  mountd
    100005    3   udp    857  mountd
    100005    1   tcp    628  mountd
    100005    3   tcp    628  mountd
    100021    1   udp    723  nlockmgr
    100021    3   udp    723  nlockmgr
    100021    1   tcp    675  nlockmgr
    100021    3   tcp    675  nlockmgr

on Linux:
lnx004:~> /usr/sbin/rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp   1024  status
    100024    1   tcp   1024  status
    100007    2   udp    965  ypbind
    100007    1   udp    965  ypbind
    100007    2   tcp    968  ypbind
    100007    1   tcp    968  ypbind
    100021    1   udp   1027  nlockmgr
    100021    3   udp   1027  nlockmgr
    100021    4   udp   1027  nlockmgr

and on Tru64:
unxc03:~> /usr/sbin/rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100007    2   tcp    971  ypbind
    100007    2   udp    973  ypbind
    100007    1   tcp    971  ypbind
    100007    1   udp    973  ypbind
    100024    1   udp   1025  status
    100024    1   tcp   1024  status
    100021    1   tcp   1025  nlockmgr
    100021    2   tcp   1025  nlockmgr
    100021    3   tcp   1025  nlockmgr
    100021    4   tcp   1025  nlockmgr
    100020    3   tcp   1025  llockmgr
    100021    1   udp   1026  nlockmgr
    100021    2   udp   1026  nlockmgr
    100021    3   udp   1026  nlockmgr
    100021    4   udp   1026  nlockmgr
    100020    3   udp   1026  llockmgr
    100011    1   udp   1034  rquotad
    100002    1   udp   1035  rusersd
    100002    2   udp   1035  rusersd
    100068    2   udp   1036  rpc.cmsd
    100068    3   udp   1036  rpc.cmsd
    100068    4   udp   1036  rpc.cmsd
    100083    1   tcp   1028  rpc.ttdbserverd
1342177279    4   tcp   1032
1342177279    1   tcp   1032
1342177280    4   tcp   1463
1342177280    1   tcp   1463

So version 4 are present in Linux and Tru64 and not in OpenBSD (as per
man page). 

I'm not totally sure nlockmgr is the culprit, after all the linux clients
seem to work anyway. But then again, it's possible they give up on the
lock. 

Does anybody have any idea?

Thanks,
Ettore 
--
Ettore Aldrovandi
ettore@hep.fsu.edu			Ph:  (850) 644 3289
http://www.hep.fsu.edu			Fax: (850) 644 6735