http://etbe.coker.com.au/2009/10/28/new-play-machine/ Linux, politics, and other interesting things Wed, 08 Feb 2012 17:45:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://etbe.coker.com.au/2009/10/28/new-play-machine/comment-page-1/#comment-21154 Andrew Pollock Wed, 28 Oct 2009 14:43:02 +0000 http://etbe.coker.com.au/?p=1399#comment-21154 The overflow /tmp thing doesn't automatically imply anything nefarious. It just means the system booted up with a full /tmp. See /etc/init.d/mountoverflowtmp The overflow /tmp thing doesn’t automatically imply anything nefarious. It just means the system booted up with a full /tmp. See /etc/init.d/mountoverflowtmp

]]> http://etbe.coker.com.au/2009/10/28/new-play-machine/comment-page-1/#comment-21153 fumble Wed, 28 Oct 2009 13:02:51 +0000 http://etbe.coker.com.au/?p=1399#comment-21153 I hope you will investigate this and blog about how they got in if you can find that out. I hope you will investigate this and blog about how they got in if you can find that out.

]]> http://etbe.coker.com.au/2009/10/28/new-play-machine/comment-page-1/#comment-21152 Sven Joachim Wed, 28 Oct 2009 12:03:02 +0000 http://etbe.coker.com.au/?p=1399#comment-21152 Actually, the only problem that the "overflow" filesystem indicates is that you were running out of disk space. Such a filesystem is mounted automatically on boot if / has no space left, see /etc/init.d/mountoverflowtmp. Actually, the only problem that the “overflow” filesystem indicates is that you were running out of disk space. Such a filesystem is mounted automatically on boot if / has no space left, see /etc/init.d/mountoverflowtmp.

]]>