🚀 go-pugleaf

"Alan Shiers" <ashiers@hfx.eastlink.ca> wrote in message
news:3D279D25.59AA52E@hfx.eastlink.ca...

>
> Then I got the bright idea...why not encorporate a threaded class as
> part of the server app that has another ServerSocket object in it set to
> listen only to the loopback address (127.0.0.1).  Then include with the
> program one additional class with its own main() method and a Socket
> object, which I can use to execute solely for the purposes to
> communicating with the running server app and tell it to shut down.
>
> That would work, wouldn't it?
>
> For those of you who are Linux savy, maybe you see some problems with
> this?
> I'd like to hear any comments you may have.
The ShutdownHook class can be used to catch the KILL signal and do just that
:)

You could knock up a nice shell script, like the one apache has, to have the
start, stop etc. presented. This could be invoked in a startup script and /
or from the command line.