https://github.com/Whonix/sdwdate/commit/429b0156c8242e2353f5c1d64406f829f90c4168 by @joysn1980 helped a lot. Showed be the correct place where to implement this.

https://github.com/Whonix/sdwdate/commit/66341d6b3232f3f812b0ac3ebd6f49a7928c543f

Maybe not the cleanest implementation. Help welcome.

Can we call /usr/bin/sdwdate's exit_handler() directly from remotes.py?

A python coding question. These two code blocks.

• /usr/lib/python3/dist-packages/sdwdate/remote_times.py excerpt: https://github.com/Whonix/sdwdate/blob/46118bba0096a2691c016f7a2f69ac60c7ece21d/usr/bin/sdwdate#L153-L154
• /usr/bin/sdwdate function check_remote excerpt: https://github.com/Whonix/sdwdate/blob/f80f39dad6da3829b01f1b5e3c668f5d26e47a3e/usr/lib/python3/dist-packages/sdwdate/remote_times.py#L33-L53

My implementation is a bit weird. Can we call /usr/bin/sdwdate's exit_handler() directly from remotes.py? @marmarek

Where the other thread is created? For me it looks like get_time_from_servers is running in the main thread, so simply not catching SystemExit should be enough. At the point where it was raised, you already called sys.exit (which is how SystemExit is raised), so exit_handler was already called.

If I'm mistaken about this, and it's running in non-main thread, you may want to use https://docs.python.org/3/library/threading.html#event-objects instead, and check it in main loop. Something like:

exit_event = threading.Event()

...

if exit_event.is_set():
  sys.exit(143)

And from the other thread:

exit_event.set()

Also, Python >= 3.4 comes with great API for concurrent execution - asyncio - much more powerful version of asyncore. In this case it could be used to avoid threads at all. But I'm still learning how to use it... You may want to read/watch this: https://fosdem.org/2017/schedule/event/python_coroutines/ if you want quick intro.