supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
Subject: s6 xinit replacement?
Date: Tue, 10 May 2022 21:36:52 -0600	[thread overview]
Message-ID: <3VJC4G8PXTKVS.3RQFDLXYQABMW@oak.localdomain> (raw)

I had the thought to start up all my personal services with s6, and it's
going well.  However, looking at the xinit source code, it appears to
start the X server, wait until it's up, start a client program, wait
until it shuts down, and then kill the X server.  It seems to me that
xinit is effectively performing process supervision on the X server and
client program.

I tried to run X under s6 with the following run file:


backtick -E screen {
	pipeline { tty } sed s:/dev/tty::

export DISPLAY :${screen}

X :${screen} vt${screen}

Unfortunately, the server never starts up, although I can run those
commands just fine from the tty.  The last few lines of my Xorg log are
the following:

(WW) xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted
Fatal server error:
(EE) xf86OpenConsole: Switching VT failed
Please consult the The X.Org Foundation support 
 for help. 
(EE) Please also check the log file at (redacted) for additional information.
(WW) xf86CloseConsole: KDSETMODE failed: Operation not permitted
(WW) xf86CloseConsole: VT_SETMODE failed: Operation not permitted
(EE) Server terminated with error (1). Closing log file.

Does anybody know anything about how s6-svscan and s6-supervise might
change the environment so as to complicate running X?  I've also checked
to see if the tty got modified, but running the tty command under s6
from the tty console gives the same output as running it directly from
the console.

Thanks for your help!

             reply	other threads:[~2022-05-11  3:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  3:36 dallinjdahl [this message]
2022-05-14  3:47 ` Guillermo
2022-05-14 23:45   ` dallinjdahl
2022-05-15  1:52     ` Laurent Bercot
2022-05-15 15:02       ` Guillermo
2022-05-17  4:10         ` Rio Liu
2022-05-15  2:44   ` Samuel Holland
2022-05-22 15:07     ` Guillermo
2022-05-22 16:33       ` Samuel Holland
2022-05-23 10:05       ` yianiris
2022-05-23 23:40         ` Guillermo
2022-05-27  2:04         ` Steve Litt
2022-05-28  4:07     ` Dallin Dahl
2022-05-28 17:15     ` Dallin Dahl
2022-05-28 19:43       ` Samuel Holland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3VJC4G8PXTKVS.3RQFDLXYQABMW@oak.localdomain \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).