Dear Managers,
Since my original summary I have received communications from
"Craig I. Hagan" <hagan_at_cih.com>
"Matt J. L. Goebel" <goebel_at_emunix.emich.edu>
Tim DiLauro <timmo_at_RacerX.mse.jhu.edu>
They had the following suggestions:
i) Do all pine transactions via imap rather than nfs. Because I run a very
heterogeneous mail environment, this isn't practical. It is the user
directories (where pine stores some folders, including the ones causing the
problems) that are NFS-exported, not the mail spool. Because this is a
college, doing away with NFS for user home directories really isn't an
option.
ii) Change the pine configuration file:
folder-collections={mail.yourdomain.edu}mail/[]
(where mail.yourdomain.edu should be the NFS server, I presume.)
This caused Pine to lock up with a "Busy" message whenever a message was sent.
(I did enable imap in the server's /etc/inetd.conf file and I sent a hangup
signal to inetd.)
iii) Set MAILLOCKING to type 5: rcmgr set MAILLOCKING 5. Per a previous post
to this list I had already done that.
iv) Using the "noac" attribute either in /etc/fstab or when mounting the NFS
filesystem. I tried this without any apparent effect.
Obviously I still have a problem; any other ideas would be most welcome.
Thanks for the above suggestions; they were all good ideas.
Larry
============================================================================
Larry Griffith Dept. of Computer & Info Science
larry_at_garfield.wsc.mass.edu Westfield State College
(413) 572-5294 Westfield, MA 01086 USA
PGP public key available at:
http://garfield.wsc.mass.edu/dcis/griffith.html
============================================================================
Received on Thu May 22 1997 - 20:39:49 NZST