The receiver service is supposed to black out the screen and get rid of the console text output when it starts up. I suspect that there is some race condition where the startup sequence undos the screen blanking. Perhaps we need to adjust the systemd service's startup dependencies to make it start later:
|
After=network-online.target |
|
Wants=network-online.target |
See output of /var/log/daemon.log:
...
Jan 4 23:52:50 piwall4 systemd[1]: Started dhcpcd on all interfaces.
Jan 4 23:52:50 piwall4 systemd[1]: Reached target Network.
Jan 4 23:52:50 piwall4 systemd[1]: Starting Permit User Sessions...
Jan 4 23:52:50 piwall4 systemd[1]: Starting OpenBSD Secure Shell server...
Jan 4 23:52:50 piwall4 systemd[1]: Reached target Network is Online.
Jan 4 23:52:50 piwall4 systemd[1]: Started piwall2 receiver.
...
The receiver service is supposed to black out the screen and get rid of the console text output when it starts up. I suspect that there is some race condition where the startup sequence undos the screen blanking. Perhaps we need to adjust the systemd service's startup dependencies to make it start later:
piwall2/install/piwall2_receiver_service.sh
Lines 7 to 8 in 0f07d51
See output of
/var/log/daemon.log: