summaryrefslogtreecommitdiff
path: root/scripts/driver
diff options
context:
space:
mode:
authorklm1998-11-03 04:43:05 +0000
committerklm1998-11-03 04:43:05 +0000
commitd0bf072246fc5b9d8ebd8a4b4cb62d13710ec835 (patch)
tree0ad992ff591f85d2a4b06c3550296c8e3867d5ba /scripts/driver
parent10f3bf437a4049f4dee2c6b03b324bdac749fa3e (diff)
downloadmailman-d0bf072246fc5b9d8ebd8a4b4cb62d13710ec835.tar.gz
mailman-d0bf072246fc5b9d8ebd8a4b4cb62d13710ec835.tar.zst
mailman-d0bf072246fc5b9d8ebd8a4b4cb62d13710ec835.zip
.ArchiveToMbox(): Remove gratuitous self.Save() - particularly
problematic in a forked image of the list - both the parent and the child have the lock, and they're both going to use it! .ArchiveMail(): Do an os._exit() instead of a return in the case where ARCHIVE_TO_MBOX is 1 (mbox only). Otherwise we were returning to a second version of the caller, and havoc ensued...-) There is still a problem with not having the final os._exit() ensured as part of a "try:...finally:" clause, which actually causes redundancy in the operation of the post script. The problem is: - the post script, for example, calls ArchiveMail() within the try section of a try...finally - ArchiveMail() may encounter an exception before it hits the os._exit() - and thus, the stack frame will be popped back to post(), hitting the finally which gets executed. I'd like to just put the ArchiveMail()'s os._exit() in a finally clause, to make sure it always happens, but for some reason that is preventing tracebacks from making their way to the error log. We need to determine why that's happening, and do the right thing, otherwise we *are* getting multiple returns from routine when an exception occurs.
Diffstat (limited to 'scripts/driver')
0 files changed, 0 insertions, 0 deletions