On Monday 14 January 2008 06:35:18 pm Aaron Kulkis wrote: > I'll admitt that I've had one -1- issue with it, when it made my box a > > > slow hog, and that was when someone sent me a borked .doc file, that > > made beagle choke. Deleted the file, and no, none, whatsoever problems > > since. > > > > That this can happen is known as far as I could find out, so I didn't > > file a bug. + the devs want the broken file in the bug, and the content > > in this file was not something I could put out in the wild. > > This is such complete bullshit by the devs. > > There is NO REASON for them to be using ANY system calls > which could result in a target file being opened for > writing, let alone unlinked. All they need to do is go > back and REMOVE the code which allows such things to > happen in the first place. > > > How in the world is a program which is SUPPOSED to be > opening files and directories with READ PERMISSION ONLY > removing *ANY* of those files????
Hmm... Where do you read that program deleted file? It was Bjørn the one that deleted file. -- Regards, Rajko -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
