JasonJAyalaP (Jason J. Ayala P.):

JasonJAyalaP created this task. Herald added subscribers: entr0py,
WhonixQubes, Patrick. Herald added a project: Whonix.

TASK DESCRIPTION Run Whonix-Workstation and control-C to prevent KDE
booting. Run sdwdate. It successfully runs and reports "sleeping
for..." The command line isn't returned.

It shouldn't return to command line when it's sleeping. It's a daemon,
not a oneshot application. Perhaps one day there should be two programs.
A long running daemon and a oneshot time setter. That may also help for
Qubes integration - there once was a --oneshot idea. But now that I
think about it, two separate programs daemon and time setter may be better.

Control-C is ineffective. I
hit control-d as well and got "sclockadj exiting" and a command line.
The second time, I only hit control-c, waiting, and

Please grep Whonix code for KeyboardInterrupt and see if these
examples can be replicated.

I didn't think it's important - what I am always doing during developing
is making changes, and then restarting the systemd service.

sudo make install && sudo systemctl restart sdwdate

(make install works for "simple" changes which are unrelated to
systemd / debian packaging. I.e. if just changing sdwdate code logic,
that is most times good enough (faster than make deb-icup).

In another window.

sudo tail -f -u sdwdate

(Because signal sigterm / sigint handling works.)

got an out of
memory error and some kind of memory/process dump.

Try increase RAM?

Perhaps the sdwdate systemd daemons needs memory and another instance in
cli is pushing it too far?