Bug#2408: Pine does not correctly lock mailboxes

[richard@uk.geeks.org (Richard Kettlewell)]

Ian Jackson writes:
>Rob Leslie writes ("Bug#2408: Pine does not correctly lock mailboxes"):

>>> 10314 uname({sys="Linux", node="sfere", ...}) = 0
>>> 10314 open("/var/spool/mail/richard.lock.825271063.10314.sfere", O_WRONLY|O_CREAT|O_EXCL, 0666) = -1 EACCES (Permission denied)
>>> 10314 stat("/var/spool/mail/richard.lock.825271063.10314.sfere", 0xbfffe718) = -1 ENOENT (No such file or directory)
>>
>>Seems very strange also the filename used here. Is the lock file not
>>supposed to be named simply "richard.lock"?
>
>It's probably going to use `link' to put it in the right place.  This
>has some beneficial effects when using an NFS-mounted mail spool
>(NEVER DO THIS, though).

That's correct.  RTFM open(2) for full details about this.  Personally
I'd use the host's IP address rather than the unqualified hostname...

--
Richard Kettlewell
http://www.elmail.co.uk/staff/richard/                    richard@uk.geeks.org
                                        Take the longest day/Waste it all away
                                      I can't stand it/But I can't do anything