On Fri, 31 Dec 2010 12:51:57 +0100 Rodolphe Rocca <maitrech...@gmail.com> wrote: > Off course every user would appreciate things to go a little bit > faster if possible here :-)
The next major release includes a workaround for some libstdc++ stupidity that tends to make it try to write() one byte at a time. That'll make a fair difference there... > >> Moreover If I CTRL-C, the resume file gets corrupted. > >> Isn't there a signal handler catching this signal and waiting for > >> the resume-file being completely written before exiting > >> gracefully ? > > No. > > Is it a design choice or a question of priority ? Due to their nature, it's basically impossible to write Unix signal handlers correctly. > Any advice on how to handle this situation ? > Because at this time I don't know how to rebuild my system with cave > without uninstalling a few packages like etqw-data... --without -- Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ paludis-user mailing list paludis-user@lists.pioto.org http://lists.pioto.org/mailman/listinfo/paludis-user
