|
From: | Lionel Bouton |
Subject: | Re: [Mldonkey-users] File corruption following, mldonkey hardening proposal |
Date: | Sun, 18 May 2003 17:02:06 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 |
Markus Hitter wrote:
Am Sonntag, 18.05.03 um 15:34 Uhr schrieb Lionel Bouton:I've seen mldonkey-2.4-1 create "empty" files in the commut directory.You're talking about the "incoming" directory, right?
Yes the one the files are commited in. (comm_u_t was a typo).
mldonkey shouldn't create anything there, except for autocommited files. I'd consider this behaviour as a bug.
I couldn't agree more !
Probably, you have switched auto-commiting off?
Yes, I want to choose the name :-)
I don't like auto-commiting for the reasons you described nicely. Obviously, even manually commiting with file-recheck doesn't make things foolproof :-(If you set incoming/ and all files therein to read-only, does this trigger anything? mlnet should work as before, IMO.
Hum, I don't want to take this risk, I've no idea what will happen if the dir is read-only when I'll commit one file.
LB.
[Prev in Thread] | Current Thread | [Next in Thread] |