Date: Sun, 8 Feb 2004 19:40:07 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> Cc: freebsd-current@freebsd.org Subject: Re: how to confuse truss: truss -f fsck -p / Message-ID: <20040209034007.GA432@xor.obsecurity.org> In-Reply-To: <m34qu1vt4b.fsf@merlin.emma.line.org> References: <m34qu1vt4b.fsf@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 09, 2004 at 04:17:40AM +0100, Matthias Andree wrote: > After typing "truss -f fsck -p /", I see nothing. I press ^Z > and type kill -9 % (killing truss). >=20 > I now have these fine processes hanging dead in memory, they are immune > to kill -9 and don't respond to kill -CONT either, ps axl: >=20 > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > 0 56974 1 0 8 0 1256 744 ppwait D p1 0:00.00 fsck -= p / > 0 56975 56974 0 8 0 1256 744 stopev DV p1 0:00.00 fsck -= p / >=20 > Is this how things are supposed to be, even though killing a tracer is > way stupid? I think it's not nice to have unkillable processes. >=20 > Is there a way to get rid of these without reboot? >=20 > Is there anything I can do to help debug this? >=20 > The software is quite current, half a day maybe. I've seen the same thing..truss appears to be broken in -CURRENT. Kris --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAJwEWWry0BWjoQKURAhXsAJ4l37aV7JULiaqE+4702QTJTbOBkwCg7a9y OwCGV6kyKf4uAW6uT3Zj/+U= =uGYX -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209034007.GA432>