Well thats it anyway, we trying to debug something that shouldn't happen in the first place :-) Can you imagine what the answer would be if you where on windows :-)
"Always close the system through the start menu and wait for the machine to shut down even if it takes 24 hours and has a bluescreen"
Anyway I tested for 0 byte files and just had a few in /proc and in /lib, here the tail for brevity
Well thats it anyway, we trying to debug something that shouldn't happen in the first place :-) Can you imagine what the answer would be if you where on windows :-)
"Always close the system through the start menu and wait for the machine to shut down even if it takes 24 hours and has a bluescreen"
Anyway I tested for 0 byte files and just had a few in /proc and in /lib, here the tail for brevity
/proc/31078/ sessionid coredump_ filter 2.6.28- 8-generic/ volatile/ .mounted
/proc/31078/
/proc/31078/io
/lib/init/rw/.ramfs
/lib/modules/
Nothing special.
Im on 64 bit Intel P4HD my other machine with Jaunty a 32 bit asus eeepc1000h shows similar behaviour