Re: [U2] Getting information on udt processes

2006-08-07 Thread Wendy Smoak
On 8/4/06, Symeon Breen <[EMAIL PROTECTED]> wrote: BTW I have found that port.status stack.trace, atleast on linux, on a unirpcd process sometimes does not work, it does not return anything ! Not sure why. Sadly, that's the case with UniData on HP-UX as well. :( :PORT.STATUS PID 3570 CALL.STAC

Re: [U2] Getting information on udt processes

2006-08-04 Thread Symeon Breen
BTW I have found that port.status stack.trace, atleast on linux, on a unirpcd process sometimes does not work, it does not return anything ! Not sure why. On 02/08/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On 8/2/06, Tom Dodds <[EMAIL PROTECTED]> wrote: > > > If you are on UniVerse it is LAYE

Re: [U2] Getting information on udt processes

2006-08-02 Thread Wendy Smoak
On 8/2/06, Tom Dodds <[EMAIL PROTECTED]> wrote: If you are on UniVerse it is LAYER.STACK instead of CALL.STACK. Thanks! I created a page on the wiki with an example of PORT.STATUS: http://www.pickwiki.com/cgi-bin/wiki.pl?ViewCallStack -- Wendy --- u2-users mailing list u2-users@listse

Re: [U2] Getting information on udt processes

2006-08-02 Thread Wendy Smoak
On 8/2/06, Timothy Snyder <[EMAIL PROTECTED]> wrote: Try PORT.STATUS PID 9 CALL.STACK. It reports the call stack, including the current line number for all executed programs and external subroutines. Thank you! That's *exactly* what I need. Now I just have to wait for it to happen again

RE: [U2] Getting information on udt processes

2006-08-02 Thread Tom Dodds
: Wednesday, August 02, 2006 2:45 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Getting information on udt processes [EMAIL PROTECTED] wrote on 08/02/2006 01:57:45 PM: > Rather than just kill the process, is there some way to get a stack > trace from it? I'd love to find out what subr

Re: [U2] Getting information on udt processes

2006-08-02 Thread Timothy Snyder
[EMAIL PROTECTED] wrote on 08/02/2006 01:57:45 PM: > Rather than just kill the process, is there some way to get a stack > trace from it? I'd love to find out what subroutine it's running. Try PORT.STATUS PID 9 CALL.STACK. It reports the call stack, including the current line number for al

[U2] Getting information on udt processes

2006-08-02 Thread Wendy Smoak
Occasionally we have some udt process that take up lots of resources and never finish. Most likely there's an endless loop in some subroutine. I know it's coming through unirpcd, because the processes are owned by a user that is only allowed to connect that way. Most likely it's in a subroutine