search

spanezz / nodm

Automatic display manager
GNU General Public License v2.0
141 stars 21 forks source link

Detect X server exit status instead of doing timeouts #18

Open midenok opened 5 years ago

midenok commented 5 years ago

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;
  3. Restart (without timeouts) or exit depending on configuration.

So timeout should be accounted only for crash and only one time (who needs X server crashing more frequently than working).

sunweaver commented 5 years ago

Tu

Am Sonntag, 28. Juli 2019 schrieb Aleksey Midenkov:

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

sunweaver commented 5 years ago

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: https://github.com/spanezz/nodm/issues/1

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

mckaygerhard commented 2 years ago

just for this issue maybe this help: https://github.com/softlab/nodm/commit/f1a0f09bee1bb6199983f527c32099d4ea0d530b

sunweaver commented 2 years ago

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.