Re: bin/27231: lockd problems

[Thomas Quinot]

Le 2001-04-23, Thomas Quinot écrivait :

 deterministic fashion. It also tends to leave the mailbox locked on the
 server even after quitting. Running lockd with debugging enabled did
 not show anything that looks like an abnormal condition.

I am still seeing this problem on -CURRENT as of:

FreeBSD shalmaneser.enst.fr 5.0-CURRENT FreeBSD 5.0-CURRENT #15: Thu Jun  7 17:54:30 
CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHALMANESER  i386

[ Cc: GNATS so the PR can be reopened. ]

Thomas.

-- 
Thomas Quinot ** Département Informatique  Réseaux ** [EMAIL PROTECTED]
  ENST   //   46 rue Barrault   //   75634 PARIS CEDEX 13 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

lockd problems

[Thomas Quinot]

Since client side locking was implemented, I am having much trouble
reading mail on an NFS-mounted mail spool.

The NFS server is a Solaris 2.6 U250, and I am reading mail using mutt.

When lockd is not running, mutt gets EOPNOTSUPP when trying to flock().
When lockd is running, it occasionnally gets EPERM, but not in a
deterministic fashion. It also tends to leave the mailbox locked on the
server even after quitting. Running lockd with debugging enabled did
not show anything that looks like an abnormal condition.

Anything I can do to resolve the problem? Or to help finding out what
is happening? :)

Thomas.

-- 
Thomas Quinot ** Département Informatique  Réseaux ** [EMAIL PROTECTED]
  ENST   //   46 rue Barrault   //   75634 PARIS CEDEX 13 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message