[Pkg-amule-devel] Bug#405709: Bug#405709: closed by Sandro Tosi <morph at debian.org> (Re: amule: aMule configuration screws up after unexpected poweroff)

Sandro Tosi morph at debian.org
Thu Dec 31 16:21:16 UTC 2009

Hello Marc,

On Thu, Dec 31, 2009 at 09:58, Marc Coll <marcoll at ya.com> wrote:
> I'm currently using ext4, and it still happens, so it's not an XFS issue.

they are the same kind of filesystem, specifically journaling
filesystems. they guarantee that the filesystem (as a whole) is always
consistent (at the cost of "sacrifying" some files/dirs).

> Besides, I don't see any reason why aMule should be constantly writing to
> amule.conf, since it's a file that should never change. Perhaps the
> [Statistics] section should be kept in a different file. Also, the files
> which are constantly being written, like the *.part files, never get lost.

They are not constantly being written: there are buffers, and if a
part file is empied, the download will restart from 0, and for each
download there is just one part file. On the contrary, on ~/.aMule
there are files shared by all the downloads (so more changes per file)
so an update to a downloading file (for example for known) will
trigger an update, multiplied for all the downloading files it
increase the chance of a file corruption.

In any case, if you experience several power loss an UPS is in order,
and to solve the amule problem, a simple backup solution is more than

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

More information about the Pkg-amule-devel mailing list