Comment 21 for bug 451289

Revision history for this message
Daniel Riedemann (darie) wrote :

>That output doesn't look like SVN 1385.

Oups, sorry... I build a package but I forgot to install it. I think I should go earlier to bed to today... :-(
Now it works and looks like this:

debug: clean_operation('system'), options = '['memory']'
debug: disabling swap
debug: running cmd ['swapoff', '-a', '-v']
debug: detected swap devices: ['/dev/mapper/swap']
info: wiping swap device '/dev/mapper/swap'
debug: running cmd ['blkid', '/dev/mapper/swap', '-s', 'UUID']
debug: uuid(/dev/mapper/swap)='c6ea33e5-0af6-4148-8a92-b0d8eddfdf1f'
debug: reinitializing swap device /dev/mapper/swap
debug: running cmd ['mkswap', '/dev/mapper/swap', '-U', 'c6ea33e5-0af6-4148-8a92-b0d8eddfdf1f']
debug: wipe_memory() pid 15519 waiting for child pid 15528
debug: new nice value 19
debug: dropping privileges of pid 15528 to uid 100
debug: physical free: 1087000576 B (1036 MB)
info: allocating 777.00 MB (814930944 B) memory
debug: wiping 777.00 MB I just allocated
warning: child process returned code 11
debug: re-enabling swap
debug: deepscans= {}
debug: searches= {}

What does bleachbit do when it wipes the swap? It goes so fast and has so less hdd activity it can't be something like a dd if=/dev/zero ...