On 23/07/2005, at 8:44 PM, Trejkaz wrote: > On Sat, 23 Jul 2005 18:35, James Bunton wrote: >> Any idea what these users are doing that triggers this? > > I think it's more what the server is doing. It happened to my own > file this > time around. My theory is, PyMSNt opened the file, truncated the > file, and > then failed to write to the file. > > The same thing might happen if there were no disk space available. > > Ideally, the updated spool file should be writetn to a new file, and > then > moved onto the name of the original file. That way, if the file fails > to be > written somehow, the original is still valid. > > The interesting thing is why the files were being written in the first > place. > No data in them actually changes after you register, AFAIK.
Data does change after you register, every time your MSN contact changes. If the disk was running out of space then an exception should be generated. Are there any exceptions in the log that correspond to these blank files? --- James
