kill -9 (kill -KILL) pulls the rug out from under a process, but many of the
other signals can be trapped. In one of the other posts, they mentioned
that <ctrl>-c was trapped, which is why I suggested -INT, but if -TERM is
also trapped (which is the default when issuing 'kill' without an explicit
argument), then it will work fine as well. You can try "man signal" and
"man kill" to learn more about signals.
Jim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Guy
> Rouillier
> Sent: Friday, May 04, 2001 11:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] problems launching JBoss2.2.x from a user
> shell
>
>
> You are correct, I tried it without the -INT and that seems to work okay.
> And yes, I do want to be able to start and stop JBoss through a command
> script. I was going to attempt this with ps and grep, but writing the pid
> to a file sounds like a better idea.
>
> I realize this is a pure Unix question and not JBoss, but I was surprised
> that "kill pid" worked to shut down JBoss normally. I thought kill just
> kind of pulled the carpet out from under the process, which thus had no
> chance to clean up.
>
> ----- Original Message -----
> From: "Robert Schulz" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 03, 2001 8:04 PM
> Subject: RE: [JBoss-user] problems launching JBoss2.2.x from a user shell
>
>
> > "kill pid" shuts it down fine. You probably want to
> > write a startup script which writes the pid into a
> > file and a stop script which reads it from a file
> > and kills it.
> >
> > R.
> >
> > > -----Original Message-----
> > > From: Jim Brownfield [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, May 04, 2001 8:34
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: [JBoss-user] problems launching JBoss2.2.x from a user
> > > shell
> > >
> > >
> > > Since "^C" supposedly shuts JBoss down gracefully, you should
> > > be able to
> > > execute "kill -INT <procid>" where "<procid>" is retrieved
> > > from a "ps"
> > > command.
> > >
> > > Jim
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Guy
> > > > Rouillier
> > > > Sent: Thursday, May 03, 2001 9:11 AM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Re: [JBoss-user] problems launching JBoss2.2.x from a user
> > > > shell
> > > >
> > > >
> > > > Having done this, is there a way to shut down JBoss gracefully,
> > > > so it has a
> > > > chance to shut down everything that is running in a controlled
> > > > fashion? Or
> > > > do you just kill the process, and hope for the best?
> > > >
> > > > ----- Original Message -----
> > > > From: "Jim Brownfield" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Thursday, May 03, 2001 11:40 AM
> > > > Subject: RE: [JBoss-user] problems launching JBoss2.2.x
> > > from a user shell
> > > >
> > > >
> > > > > Hi Juan,
> > > > >
> > > > > try "nohup ./JBoss2.2.1/bin/run.sh &"
> > > > >
> > > > > This should keep the terminal group from axing your JBoss
> > > > subprocess when
> > > > > the terminal exits.
> > > > >
> > > > > Jim
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: [EMAIL PROTECTED]
> > > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > > > Juan Arraiza
> > > > > > Sent: Thursday, May 03, 2001 2:03 AM
> > > > > > To: [EMAIL PROTECTED]
> > > > > > Subject: [JBoss-user] problems launching JBoss2.2.x
> > > from a user shell
> > > > > >
> > > > > >
> > > > > > Hi all,
> > > > > > We are founding trouble when launching JBoss2.2.x as a
> > > background
> > > > > > process from a user shell in Solaris 2.6. If we close that
> > > > user terminal
> > > > > > (or finish the X-Windows session) from which we have
> > > launched JBoss,
> > > > > > JBoss dies.
> > > > > >
> > > > > > We launch JBoss typing:
> > > > > > ./JBoss2.2.1/bin/run.sh &
> > > > > >
> > > > > > In theory (although I confess I am not a great expert
> > > in Unix), that
> > > > > > process we start does not depend on the terminal from
> > > which we have
> > > > > > launched it (since it is launched as a background
> > > process). As I said,
> > > > > > when we close that terminal, the process dissapears with it.
> > > > > >
> > > > > > Does anybody know why?
> > > > > >
> > > > > > TIA
> > > > > >
> > > > > > Juan
> > > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > JBoss-user mailing list
> > > > > [EMAIL PROTECTED]
> > > > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > JBoss-user mailing list
> > > > [EMAIL PROTECTED]
> > > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> >
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
