On 05/28/2006 02:33 PM, Colm MacCarthaigh wrote: > On Sun, May 28, 2006 at 10:32:04AM -0000, [EMAIL PROTECTED] wrote:
> > A significant source of this kind of error is that the filesystem > suddenly becomes read-only. Either to a protective automative re-mount > by the kernel, a log journal becoming full, in which case the remove > will also fail :/ Thats true, but 1. In this case no further temporary files get created anyway. 2. Trying to remove it does not really hurt, even if it fails. OTH if becoming read-only is not the source of the error we clean things up. Regards Rüdiger
