man nohup
Cheers,
R.
User Commands nohup(1)
NAME
nohup - run a command immune to hangups
SYNOPSIS
/usr/bin/nohup command [ argument ... ]
/usr/xpg4/bin/nohup command [ argument ... ]
DESCRIPTION
The nohup utility invokes the named command with the argu-
ments supplied. When the command is invoked, nohup
arranges for the SIGHUP signal to be ignored by the process.
The nohup utility can be used when it is known that command
will take a long time to run and the user wants to logout of
the terminal; when a shell exits, the system sends its chil-
dren SIGHUP signals, which by default cause them to be
killed. All stopped, running, and background jobs will
ignore SIGHUP and continue running, if their invocation is
preceded by the nohup command or if the process programmat-
ically has chosen to ignore SIGHUP.
> -----Original Message-----
> From: Juan Arraiza [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 03, 2001 19:03
> 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
