Home › Forums › kdb+ › Prevent a q application from exiting when it doesn’t have a port. › Re: Prevent a q application from exiting when it doesn’t have a port.
-
Perhaps the answer is in your question; if a q process is not actively executing e.g. a script, listening on a port to process some work or connected to stdin (interactive mode), then what is it’s purpose?
From the perspective of the process, there is nothing left to do and thus doesn’t need to be running. That would be my guess as to why this is the default behavior built into the binary.
Perhaps someone closer to core implementation will be able to share more insight.