Bill,
I agree with Deepak, that app must not be releasing all the resources. This
might be a silly question, but what options do you have for debugging the
app?
...Kevin
> -----Original Message-----
> From: plug-discuss-admin@lists.PLUG.phoenix.az.us
> [mailto:plug-discuss-admin@lists.PLUG.phoenix.az.us]On Behalf Of Bill
> Warner
> Sent: Friday, February 16, 2001 2:52 PM
> To: plug-discuss@lists.PLUG.phoenix.az.us
> Subject: Re: server went down
>
>
> UID PID PPID C STIME TTY TIME CMD
> joeuser 31023 1 0 15:29 ? 00:00:00 -sh
> joeuser 23174 1 0 16:56 ? 00:00:00 -sh
> joeuser 32042 31023 0 16:57 ? 00:00:00 run MS/MS.START
> joeuser 32092 23174 0 16:57 ? 00:00:00 sh /bin/GO
> joeuser 32192 32092 0 16:57 ? 00:00:00 sh /bin/GO
>
> This is an example of some of the procs that are left after a logout.
> i noticed the the -sh procs have moved to init as there parent process??
> is there a configureation for init to clean upthese procs or is it likly
> something
> in the scripts that are holding them open???
>
> Bill Warner
>
> On 16 Feb 2001 13:31:35 -0500, Deepak Saxena wrote:
> > > What in a program can cause it not to die when your session
> is over? and
> > > what can i do to help clean these up rather than just haveing greping
> > > them out
> > > of a ps and killing them?
> >
> > If a program doesn't die when the session is over, it generally means
> > that it's somehow still atached to a tty or something of that sort.
> >
> > ~Deepak
> >
> > >
> > > --
> > > --
> > > Bill Warner
> > > Direct Alliance Corp.
> > > Unix/Linux Admin.
(text/plain)