possible problem with run_queue (PR#155)

Bug #265255 reported by Bug Importer
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Unassigned

Bug Description

Jitterbug-Id: 155
Submitted-By: <email address hidden>
Date: Tue, 9 Nov 1999 05:19:32 -0500 (EST)
Version: 1.0
OS: Linux 2.2.13

I get the following output from the cron command
/usr/local/mailman/cron/run_queue

Traceback (innermost last):
  File "/usr/local/mailman/cron/run_queue", line 46, in ?
    main()
  File "/usr/local/mailman/cron/run_queue", line 39, in main
    lockfile.lock()
  File "/usr/local/mailman/Mailman/flock.py", line 175, in lock
    os.unlink(self.tmpfname)
os.error: (2, 'No such file or directory')

This is a regular occurance, but has no obvious detremental effects ...
yet.
Looking at the code this appears to be a issue of lock contention (sp?) and
I'm
guessing its not serious. Perhaps I should simply redirect the output to
/dev/null
but since this is not whats supplied in crontab.in I assume I need to see
the
output of the run_queue command

====================================================================
Audit trail:
None

[http://sourceforge.net/tracker/index.php?func=detail&aid=214133&group_id=103&atid=100103]

Revision history for this message
Barry Warsaw (barry) wrote :

run_queue has been replaced by qrunner

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.