Subject: Pine claims folder locked when it's not

From: [email-masked] (David Kozinn)
Date: Tue, 21 Mar 1995 22:56:08 GMT

I've built Pine 3.91 on an system running HP-UX 9.04.  I've run into a
problem where when pine tries to write the Fcc to the sent-mail file, it
thinks that there's a lock on that file and it waits a while for the
lock to open (which it never does) before overriding the lock and
writing the file.  I know that there is no process with a real lock open
on that file, and I can't find a file that looks like a lock file either
in my mail directory, the spooled mail directory, or in /tmp.

I'm running "standalone" (i.e., I'm not communicating with imapd) since
this is running locally on the HP system.  Any suggestions as to where I
might look to figure out what's causing this problem?
-- 
 David Kozinn                   [email-masked] / [email-masked]
 Computer Sciences Corporation  Under contract to Mutual of New York
 Technology Managment Group     +1-201-907-6990

---

From: [email-masked] (David Kozinn)
Date: Fri, 24 Mar 1995 14:34:36 GMT

Well, upon further investigation it appears that the problem is related
to the fact that the system that we're running on has short filesystem
names (limited to 14 characters).  (HP-UX supports long names, but we're
using 14 for "historical" reasons.)  What's happening is that the
locking routine bezerk_lock() tries to create a pair of lock files
linked together, but the second creation fails because the name is not
unique at the point where the additional info is tacked onto the
original file name.

Has anyone else run into this problem, and if so, is there a simple
solution (other than converting to long filenames)?
-- 
 David Kozinn                   [email-masked] / [email-masked]
 Computer Sciences Corporation  Under contract to Mutual of New York
 Technology Managment Group     +1-201-907-6990

---

From: Muhammad Sulayman <[email-masked]>
Date: Wed, 22 Mar 1995 22:37:54 -0800

Hi,

I am having a similar problem w/ Pine on my Linux system.

Everytime I try and open my folder (incoming mail), I get the following 
error:
	Can't get write access to folder, access is read only.
	Folder open, Failed. Abort: Permission denied.

The strange thing is that my sent-mesages box works fine. And moreover, 
everything was working fine on my system for nearly a week and just 
started when I was in root mode. All the old accounts that I had set up 
for my friends show the same problem: I am told that access is read only 
for just the INBOX while the other boxes work fine.

Why did this problem come up only now? Why does this problem persist even 
when I reboot the whole system?

Thanks.

Muhammad