問題タブ [inetd]
For questions regarding programming in ECMAScript (JavaScript/JS) and its various dialects/implementations (excluding ActionScript). Note JavaScript is NOT the same as Java! Please include all relevant tags on your question; e.g., [node.js], [jquery], [json], [reactjs], [angular], [ember.js], [vue.js], [typescript], [svelte], etc.
gdb - gdb を開始できませんでした - リモートの下位デバッガーへの DDD
リモート マシンで DDD を gdb に接続しようとしています。マシンとユーザー名のパスを必要としないように rsh を構成しました。
ddd が「rtx5:1234: not found」で開き、「GDB could not be started」というポップアップが表示されます。ddd の呼び出しから --host rtx5:2159 --trace --no-exec-window /home/murray/beer-process
ddd がトレースログから起動した GDB の PID は 4 桁です。ただし、rtx(target) から確認できる PID はすべて 8 桁です。gdb をプロセスとして見ることはできませんが、トレース ログにはそれ以外のことが示されています。ドキュメンテーションは古くなっていますか? 間違って呼び出していますか? ddd が正しく rsh-ing されているかどうかをテストするにはどうすればよいですか?
ドキュメント 2.4.1の警告に対処しました。
- Beer-process バイナリは、ターゲット上のユーザー名のホーム ディレクトリにあります。
- /usr/bin/gdb で gdb のパスを確認しました
- rtx5 には xterm がないため、 --no-exec-window フラグを含めます
前もって感謝します
web-services - Are there any known Linux inetd/"wait"-capable web servers with graceful idle shutdown?
I would like to start a web server on-demand as an inetd "tcp/wait" service which shuts itself down after a programmable period of inactivity.
Many web servers already support inetd "tcp/nowait" mode, but this mode has the disadvantage that a new process needs to be forked for every new connection. It is therefore slower and more resource-intensive than running a dedicated server daemon.
A web server supporting inetd's "tcp/wait" would only be launched by inetd for the first request, then serve any number of requests using the same server instance until no requests occurred for some period of idle time, in which case the server instance automatically terminates and lets inetd start it again once the next period of activity starts.
Such a tcp/wait inetd web server should have approximately the same efficiency as a dedicated web server (i. e. running permanently) during times of activity. However, it will automatically shut down in times of inactivity, saving system resources.
Irregular "anti-demand"-driven shutdowns will also clean up any memory leaks from the web server and possibly associated FGCI-services (which would terminate together with the web server).
I know that it is already possible to use systemd's socket activation in combination with lighttpd's -i option to implement what I want.
However, I want a solution that also works without systemd, depending on nothing else than a running Internet superserver no matter how the latter one has been started (inetd/xinetd started by sysvinit, runit, manually, or systemd's socket activation replacing inetd/xinetd).