Detect X server exit status instead of doing timeouts about nodm

[sunweaver]

Tu Am Sonntag, 28. Juli 2019 schrieb Aleksey Midenkov:

…

-- Gesendet von meinem Fairphone2 (powered by Sailfijsh OS).

[sunweaver]

Am Sonntag, 28. Juli 2019 schrieb Aleksey Midenkov:

…

There are 3 reasons why server exited: 1. Crash; 2. Configuration error; 3. User initiative (including Ctrl + Alt + Backspace). Usually they are differentiated by exit code (it also includes signal which caused termination). That's what nodm must do correspondingly: 1. Restart and if crashed again in short timeout exit without further restarts; 2. Exit immediately;o 3. Restart (without timeouts) or exit depending on configuration. So timeout should accounted only for crash and only one time (who needs X server crashing more frequently than working). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #1

-- Gesendet von meinem Fairphone2 (powered by Sailfish OS).

[mckaygerhard]

just for this issue maybe this help: softlab@f1a0f09

[sunweaver]

just for this issue maybe this help: softlab@f1a0f09

I just dropped @softlab a note via his nodm fork on Github. The nodm display manager is in deep need for another upstream maintainer. I pinged @softlab if he'd be willing to step up for this job. It needs someone who uses nodm on a regular basis and who encounters errors when they pop up.

Neither @spanezz nor myself (@sunweaver) are maintaining nodm actively anymore. I have also stopped using it (because I lack the customer use cases these days). But, still, I think that nodm fills a gap in the display manager universe.