Am Sonntag 02 Mai 2010 schrieb Celejar: > Thanks for the explanation. But the disk is not always available, > and I sometimes want to run aMule when the disk isn't there. In > such a case, isn't the directory still deleted?
Exactly. > Perhaps there could be some sort of option to mark certain special > directories as 'persistent', so this way we could have the best of > both worlds. This would need a change of the config file, which isn't used only by aMule. We don't care much about the mods out there, but emule has to be able to read these files, too. Beside the fact that there is a change for the gui needed to implement this, and these files are still locked. > Regarding the problem of having constant 'file not found' errors, > there's anyway a "Reload shared files" button on the shared files > page. Why not just mark any files or directories not found as > 'inactive' or something, and recheck them when the user hits that > button? The problem with this is, that only dirs are shared. We don't care about single files in this part of the source. The easiest way for you is to just insert the dir, when you plug the disk in. echo "your-mountpoint" >> ~/.aMule/shareddir.dat and then reloading the shared files should do the trick. With the right udev-rules you can automate this, too. -- MfG usw. Werner Mahr registered Linuxuser: 295882 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org