Menu
▾
▴
[ archivemail-Bugs-1753702 ] crashes on zero-size mbox folder.
|
From: SourceForge.net <no...@so...> - 2008-01-19 02:04:53
|
Bugs item #1753702, was opened at 2007-07-13 19:36 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Invalid Priority: 5 Private: No Submitted By: Jonathan Ciesla (limburgher) Assigned to: Nikolaus Schulz (nikosch) Summary: crashes on zero-size mbox folder. Initial Comment: Traceback (most recent call last): File "/usr/bin/archivemail", line 6, in <module> main() File "/usr/share/archivemail/archivemail.py", line 686, in main archive(mailbox_path) File "/usr/share/archivemail/archivemail.py", line 1125, in archive new_temp_dir = tempfile.mkdtemp('archivemail') File "/usr/lib/python2.5/tempfile.py", line 320, in mkdtemp dir = gettempdir() File "/usr/lib/python2.5/tempfile.py", line 262, in gettempdir tempdir = _get_default_tempdir() File "/usr/lib/python2.5/tempfile.py", line 209, in _get_default_tempdir ("No usable temporary directory found in %s" % dirlist)) IOError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/root'] Happens on some empty folders. Does not happen on others. Not sure why, all the listed temp dirs exist on my systems. If I edit my wrapper script to only run archivemail against nonzero size boxes, i only get one error. Not sure who, but I have one user who's at quota. I'm the Fedora maintainer for this, so I'll submit a patch if I find a solution. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2008-01-19 03:04 Message: Logged In: YES user_id=1594781 Originator: NO This doesn't look like an archivemail bug. Jonathan, you've got a last chance to pick it up, otherwise the BTS bot will close this tracker in the next days. :-) ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 18:12 Message: Logged In: YES user_id=1594781 Originator: NO I strongly doubt newer archivemail versions will behave differently. Can we agree to close this bug? Looks like it's just the quota that's barfing, so it's not related to archivemail. ---------------------------------------------------------------------- Comment By: Jonathan Ciesla (limburgher) Date: 2007-11-09 12:08 Message: Logged In: YES user_id=791236 Originator: YES Actually, you're right, it is quota related. Though it may not occur with 0.7.1, so I'll check and let you know. ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 04:23 Message: Logged In: YES user_id=1594781 Originator: NO I don't see how this relates to the mailboxes in question, since at this point, archivemail may have checked if the mailbox exists, and may have seteuid() to the owners uid, but it has not yet opened the mailbox. The error is pretty bizarre. Did you try to track this down? I would guess this might be related to your quota, although I barely know about quotas. :-) Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 |
