Bob R wrote: > >I short-circuited the cron to run now, and it does indeed move on to the >next list: > >Traceback (most recent call last): > File "/usr/lib/mailman/cron/checkdbs", line 203, in <module> > main() > File "/usr/lib/mailman/cron/checkdbs", line 86, in main > mlist = MailList.MailList(name) > File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ > self.Lock() > File "/var/lib/mailman/Mailman/MailList.py", line 161, in Lock > self.__lock.lock(timeout) > File "/var/lib/mailman/Mailman/LockFile.py", line 243, in lock > self.__write() > File "/var/lib/mailman/Mailman/LockFile.py", line 422, in __write > fp = open(self.__tmpfname, 'w') >IOError: [Errno 2] No such file or directory: >'/var/lib/mailman/locks/differentlist.lock.mydomain.com.1200.0'
OK. so none of the crons are able to create locks for any list. Although it's puzzling why it's error 2 when run by cron and error 13 when run from the command line as the same user. >:/www/lists/conf$ ls -ld /var/lock/mailman >drwxrwsr-x 2 root list 80 Mar 27 18:31 /var/lock/mailman How about ls -ld /var/lock -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
