Yes, thanks for reply.
We will be eventually using it on Unix machine, at at this point, we are
running under Windows environment. That is where I am really hoping to
see if there is more graceful way of exiting other than killing through
the task manager or Ctrl+C (which hangs for a long time).
Max Levinson wrote:
Hi Ekaterina,
I know you are asking Norman, but I am the one who faced the same problem
recently, there are two possible solutions to that, first to run a starting
script in a background:
*./run.sh > /path/to/james/log/james.log &*
*
*
*In this case you'll need to manually kill the process which is not a good
solution sometimes.*
*
*
*This is the easiest way, the second way is a special startup script which
will allow you to start it Red hat style, like*
*
*
*james start*
*
*
*I think if you use most recent trunk, Norman and the rest of the team
embedded script which is called James which will start James as a normal
application. This script is located in path/to/james/trunk/bin/james*
*
*
*Hope it will help you.*
2010/5/5 Ekaterina Davydenko <[email protected]>
Hi Norman,
We are starting James server from the command line for logging and
debugging purposes. How could I gracefully exit the process? It seems to be
hanging for a long time when I do Ctrl+C.
Thanks,
Ekaterina.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
