Re: non-responding processes after truss(1)ing
On Tue, Sep 27, 2011 at 09:28:56AM -0400, Mark Saad wrote: > On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis wrote: > > On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: > >> > >> kill -9 your truss processes; the underlying processes which you are > >> truss'ing will probably resume. > >> > >> My experience for years has been that truss on FreeBSD is extremely > >> buggy and cannot be relied upon (case in point). ??Such is still the case > >> on RELENG_8 as of today. > >> > >> Use ktrace(1) instead. ??You'll find it to work pretty much in every > >> situation. > >> > > What about using dtruss in place of truss is the dtrace implementation > of truss any better then the old libkvm ? This pulls in a whole can of worms. Getting DTrace to work on FreeBSD is a little tricky, because certain commands/arguments must be provided manually during world/kernel "make" time and not via make.conf/src.conf. AFAIK this is still the case in RELENG_8, while "kludges and hacks" have been put in place on 9.x to work around this. I can provide some references to my claims if need be. There's also some segregation between DTrace-capable userland and DTrace-capable kernel, but the delineation between the two -- and how to accomplish one without the other -- is something I've never found any conclusive write-up on or otherwise. I think such an explanation would benefit many userland application authors/developers. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: non-responding processes after truss(1)ing
On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis wrote: > On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: >> >> kill -9 your truss processes; the underlying processes which you are >> truss'ing will probably resume. >> >> My experience for years has been that truss on FreeBSD is extremely >> buggy and cannot be relied upon (case in point). Such is still the case >> on RELENG_8 as of today. >> >> Use ktrace(1) instead. You'll find it to work pretty much in every >> situation. >> What about using dtruss in place of truss is the dtrace implementation of truss any better then the old libkvm ? > > Thanks, that worked. I'll use ktrace from now on. > > Nikos > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- mark saad | nones...@longcount.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: non-responding processes after truss(1)ing
On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: kill -9 your truss processes; the underlying processes which you are truss'ing will probably resume. My experience for years has been that truss on FreeBSD is extremely buggy and cannot be relied upon (case in point). Such is still the case on RELENG_8 as of today. Use ktrace(1) instead. You'll find it to work pretty much in every situation. Thanks, that worked. I'll use ktrace from now on. Nikos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: non-responding processes after truss(1)ing
On Tue, Sep 27, 2011 at 12:57:11PM +0300, Nikos Vassiliadis wrote: > My system have two non-responding processes after some truss(1)ing > i did on them. They seem stopped and do not respond to sigcont. > > >%ps > > PID TT STAT TIME COMMAND > > 9768 0- I 0:00.12 truss -p 9739 > > 9514 1 Is 0:00.29 -csh (csh) > > 9739 1 TX+2:06.24 sqlite3 ../nikos_output_actives.tst/database.db > > 7821 4- TX+0:33.62 python active.py > > 7828 4- I 0:00.57 truss -p 7821 > > 9848 5 Ss 0:00.23 -csh (csh) > >10053 5 R+ 0:00.00 ps > >% > > it's not actually 8.2-STABLE, but 8.2-RELEASE-p1, are there any > fixes in -STABLE regarding this problem? kill -9 your truss processes; the underlying processes which you are truss'ing will probably resume. My experience for years has been that truss on FreeBSD is extremely buggy and cannot be relied upon (case in point). Such is still the case on RELENG_8 as of today. Use ktrace(1) instead. You'll find it to work pretty much in every situation. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
non-responding processes after truss(1)ing
Hi, My system have two non-responding processes after some truss(1)ing i did on them. They seem stopped and do not respond to sigcont. %ps PID TT STAT TIME COMMAND 9768 0- I 0:00.12 truss -p 9739 9514 1 Is 0:00.29 -csh (csh) 9739 1 TX+2:06.24 sqlite3 ../nikos_output_actives.tst/database.db 7821 4- TX+0:33.62 python active.py 7828 4- I 0:00.57 truss -p 7821 9848 5 Ss 0:00.23 -csh (csh) 10053 5 R+ 0:00.00 ps % it's not actually 8.2-STABLE, but 8.2-RELEASE-p1, are there any fixes in -STABLE regarding this problem? Thanks! Nikos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
