Hello,
a) I don't see the point of the 'basexserverstop' and 'basexhttpstop' scripts. If I run the server as a foreground process, the only way of stopping it (that I'm aware of) is to press CTRL-C, in which case there is no opportunity to run 'basexserverstop'. If I run the server as a background process, how will the 'basexserverstop' script know which process ID to kill?
b) Please can I have a login for the documentation wiki? I think I tried applying through the site, but didn't receive a response.
Best regards,
Thomas
Dear Thomas,
Thanks for your registration; I've confirmed your account. I'm still on vacation, but I'll probably give you feedback on a) later this week.
Cheers Christian
Am 08.05.2017 13:27 schrieb "Thomas Daly" letterbox@daladi.com:
Hello,
a) I don’t see the point of the ‘basexserverstop’ and ‘basexhttpstop’ scripts. If I run the server as a foreground process, the only way of stopping it (that I’m aware of) is to press CTRL-C, in which case there is no opportunity to run ‘basexserverstop’. If I run the server as a background process, how will the ‘basexserverstop’ script know which process ID to kill?
b) Please can I have a login for the documentation wiki? I think I tried applying through the site, but didn’t receive a response.
Best regards,
Thomas
Hi Thomas,
If I run the server as a background process, how will the ‘basexserverstop’ script know which process ID to kill?
If you run basexserverstop, the server that is running on the specified port will be stopped. An empty file will be written to the local temporary directory, the server will be called, and the server will shut down gracefully.
If you work with the BaseX HTTP server, you can specify a port to stop Jetty (which is by default 8985). This port will be addressed if you call basexhttpstop.
Hope this helps. Christian
b) Please can I have a login for the documentation wiki? I think I tried applying through the site, but didn’t receive a response.
Best regards,
Thomas
basex-talk@mailman.uni-konstanz.de