Hi Pascal,
yes, this is a known issue, as we'd need to open yet another port for stopping Jetty (unfortunately, there is no other way to do this). I've added a GitHub issue:
https://github.com/BaseXdb/basex/issues/244
Hope this helps, Christian ___________________________
On Sat, Oct 22, 2011 at 9:37 PM, Pascal Heus pascal.heus@gmail.com wrote:
Hi: Under linux, I use the basexhttp script in the bin folder to start the BaseX server and Jetty HTTP server (for REST and Webdav)
To stop the process, I then copied the file into basexhttpstop nd added the stop keyword to the last line: java -cp "$CP" $VM org.basex.api.BaseXHTTP "$@" stop
However, this only seems to affect the BaseX server (Jetty continues to run and listen on port 8984). I can of course kill the process but would prefer for this to be available from the command line. Could this be adjusted?
thanks *P _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk