Very interesting....We've NEVER had this problem before, but good to know how to fix it if it does occur. I wonder how our setups are that much different.
Thanks for your perserverance in figuring this out. -----Original Message----- From: Chris Boyce [mailto:[EMAIL PROTECTED] Sent: Thursday, December 23, 2004 10:58 AM To: JRun-Talk Subject: RE: Starting JRun4 in command line locks tty > There is no reason a tty instance (secure/ssh or telnet) would cause > this issue, so I don't think it's an ssh issue. Actually, it appears this is exactly what the problem is. I googled around the ssh groups and discovered that ssh will hold your tty open if the program you back-grounded still has standard-in, standard-out, and standard-err open. Nothing technically wrong with ssh... I think it's just the way JRun4 holds open in/out/err. Redirection is the key to solving this, however, I was redirecting only output and error (not standard-in). Problem solved simply by directing /dev/null into JRun like so: ./jrun -config ./${SERVER}.config -nohup -start ${SERVER} < /dev/null 1>>${STANDARD_OUT_LOG} 2>>${STANDARD_ERR_LOG} Ssh window now closes properly on exit. Thanks! -Chris > On Tue, 2004-12-21 at 15:25 -0700, Jeffrey Anderson wrote: > > On 12/21/04 2:35 PM, "Chris Boyce" <[EMAIL PROTECTED]> wrote: > > > > > When I start JRun4 servers on the command line (UNIX) they appear > > > to lock the tty I'm in; meaning, when I eventually try to logout, > > > my terminal window is held open and must be closed by force. > > > > Are you on the local server in the console window or remotely logged > > in via ssh? > > > > Here's the command line we use for our linux install: (should be the > > same for unix too...) > > > > /<jrun-install-dir>/bin/%> ./jrun -nohup start <server> & > > > > What does your command line look like? > > > > > > > This happens even though I am running the server with -nohup. > > > This also never happened in JRun3. > > > > > > Does anyone know how to prevent this so I can gracefully logout? > > > > > > thanks > > > > > > > Usually, I just remotely log into the console via ssh to start up > > the admin application server, and then start all subsequent servers > > off of the web application. That way if you need to terminate the > > admin server, you can do so without taking the other servers down with it. > > So if you are getting the issue where your terminal session ending > > takes the jrun process with it, it will only take the admin server > > process and leave all the other servers running. > > > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - CFDynamics http://www.cfdynamics.com Message: http://www.houseoffusion.com/lists.cfm/link=i:8:5619 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/8 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:8 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.8 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
