I've just installed the mailman 2.1.2-7 package on a Debian sarge
(testing) system, and qrunner goes into an apparent infinite loop as
soon as it starts. Here's a snapshot from "top" shortly after running
"/etc/init.d/mailman start":
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ C
At 6:06 PM -0400 2003/08/19, Barry Warsaw wrote:
ok, but how do you make sure the file is really on disk instead of,
e.g., half on disk and half on cache?
We close the file before we rename it.
Do you fsync() the directory after the close and before the rename?
--
Brad Knowles, <[EMAIL PROTEC
On Monday 25 August 2003 10:15, Brad Knowles wrote:
> >> ok, but how do you make sure the file is really on disk instead of,
> > We close the file before we rename it.
> Do you fsync() the directory after the close and before the rename?
According to python documentation (os module), this
On Monday 25 August 2003 22:11, Simone Piunno wrote:
> > Do you fsync() the directory after the close and before the rename?
Ah, I've found what you were meaning...
this is from PosixFilesystem.py (ZODB implementation):
import os
from posix import fsync
def sync_directory(self,dir):
At 10:11 PM +0200 2003/08/25, Simone Piunno wrote:
fsync(fd)
Force write of file with filedescriptor fd to disk. On Unix, this calls the
native fsync() function; on Windows, the MS _commit() function.
If you're starting with a Python file object f, first do
f.flush(), and then
do o
