[Mailman-Users] Is this a bug, or just because I called it from an unpriveledged account?

Scott Brown scott-brown at home.com
Fri Dec 22 05:33:17 CET 2000

Hi Dan,

I suspected as much - I invoked it from one of the virtual domain accounts
on my server (which kinda bothers me that a virtual domain can get access to
that directory tree... though obviously cant fiddle with it's contents)

But this does leave an underlaying question though:

If it's trying to delete a lock file, it's no doubt due to the fact that it
(thought that it) created a lock file. Since no lock file is present... why
did it get as far as it did without producing an error?

(putting on my programmer's hat for a minute)

My feeling is that if it couldnt create the lock file, it should have died
there and then, or politely told the user that they're not priveleged to run
the routine (since it's a safe bet that if it couldnt create a lock file, it
couldnt create any other required files or open any datafiles for updating)

(back to mailman-user mode)

> -----Original Message-----
> From: Dan Mick [mailto:Dan.Mick at West.Sun.COM]
> Sent: Thursday, December 21, 2000 9:02 PM
> To: scott-brown at home.com
> Cc: mailman-users at python.org
> Subject: Re: [Mailman-Users] Is this a bug, or just because I
> called it
> from an unpriveledged account?
> > Traceback (most recent call last):
> >   File "./newlist", line 223, in ?
> >     main()
> >   File "./newlist", line 219, in main
> >     mlist.Unlock()
> >   File "/home/mailman/Mailman/MailList.py", line 1348, in Unlock
> >     self.__lock.unlock(unconditionally=1)
> >   File "/home/mailman/Mailman/LockFile.py", line 306, in unlock
> >     os.unlink(self.__tmpfname)
> > OSError: [Errno 13] Permission denied:
> > '/home/mailman/locks/<site>.lock.apollo.host-ops.com.6611'
> >
> > no files (at all) exist in /home/mailman/locks/ - but what
> bothered me was
> > the "<site>" stuck in there.
> >
> > Anyone care to venture a suggestion?
> looks correct.  The problem is not the name; <site> appears to be
> intentional.  Looks like the newlist process doesn't have permission
> to unlink from /home/mailman/locks.

More information about the Mailman-Users mailing list