On Fri, 2005-04-01 at 03:13 -0500, Nick Mathewson wrote: > On Fri, Apr 01, 2005 at 09:24:51AM +0200, Marco A. Calamari wrote: > > On Wed, 2005-03-30 at 15:02 -0500, Nick Mathewson wrote: > > > On Tue, Mar 29, 2005 at 08:57:25PM +0200, Leonardo Giacomelli wrote: > > > > Nick Mathewson wrote: > > > > > > > > >>Installing a mixminion 0.0.7.1 from debian Sarge, give a perfectly > > > > >> working node, except that it doesn't remove packet from > > > > >> queues when packets pass from one queue to the other and get sent. > > > > > > > > > > > > > > > How strange! Do the packets get renamed to "rmv_......" and left like > > > > > that, or do they not get renamed at all? > > > > > > > > Hi Nick, > > > > > > > > Yes, the packets has rmv_* prefix.. and it stays in incoming and > > > > outgoing dirs. What's happen? > > > > > > Not sure yet. When you set ShredCommand in the configuration file to > > > "rm -f", does anything get better? > > > > Replacind in ShredCommand "shred" with "rm" solved the problem; weird ! > > It was "shred" before? That was probably the problem. "shred" on its > own does not actually remove files. Try "shred -u" instead. I didn't any try. Both Mixminion installation were running with all default, and the ShredCommand parameter was commented. So shred were running with default parameter passed by the python code. Feel free to require more testing to me if debugging this problem can be useful for Mixminion. Thanks a lot. Marco > > > The mixminion sw has some provision to drop old packet if the filesystem > > in which the queues are became almost full ? > > Not yet. > > > yrs, -- "Oggi e' il domani di cui ci dovevamo preoccupare ieri."
Attachment:
signature.asc
Description: This is a digitally signed message part