potiuk commented on PR #22588: URL: https://github.com/apache/airflow/pull/22588#issuecomment-1121331469
> @potiuk I had similar thoughts reading the issue that there should be some configuration difference between using the cli to print configuration and the actual scheduler process. I guess we can have the configuration part to be dumped only when we send a signal sent to scheduler process since there is no consensus on cli option to print or printing by default during startup etc. The signal is nice, but I think many people do not even know how to send a signal to their process when it runs on a remote system or they might not have enough permissions to do so, but they can see the logs: https://man7.org/linux/man-pages/man2/kill.2.html > For a process to have permission to send a signal it must either be privileged (under Linux: have the CAP_KILL capability), or the real or effective user ID of the sending process must equal the real or saved set-user-ID of the target process. In the case of SIGCONT it suffices when the sending and receiving processes belong to the same session. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
