supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: Runit on tty1
Date: Fri, 30 Jun 2006 09:27:59 +0000	[thread overview]
Message-ID: <20060630092759.27727.qmail@c80d5cd64668b0.315fe32.mid.smarden.org> (raw)
In-Reply-To: <44A4EA83.5080800@langside.org.uk>

On Fri, Jun 30, 2006 at 10:10:27AM +0100, Richard Downing wrote:
> Richard A Downing FBCS CITP wrote:
> >Further investigation reveals that runit, as process 1, is marked by
> >ps-ef as being on tty1 and the bash process started by getty-1 is marked
> >as ? for it's TTY.  I suspect this is the problem, as it is quite unlike
> >my other runit-based systems.
> >There are no errors in the runsvdir proctitle.
> >
> >Does anyone have any idea what has gone wrong?
> 
> I've just upgraded to runit-1.6.0, but I have the same problem.  What 
> could cause runit to be connected to tty1?

I'm not sure, sorry.  This is what the runit program does:

 o on startup open /dev/console and set controlling terminal through
    ioctl(ttyfd, TIOCSCTTY, (char *)0) (if possible)
 o forking stage 1, which should have full control of console to start an
   emergency shell for example, runit reopens /dev/console read-write
 o forking stage 2 or 3, runit drops the controlling tty through
    setsid()

See src/runit.c, you could test removing the ioctl(), or adding setsid()
at some place.  Please report back if you happen to find out what's
different on your system.

Thanks, Gerrit.


  reply	other threads:[~2006-06-30  9:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 19:26 Richard A Downing FBCS CITP
2006-06-30  9:10 ` Richard Downing
2006-06-30  9:27   ` Gerrit Pape [this message]
2006-07-05 15:08 ` Charlie Brady
2006-07-05 16:11   ` Milan P. Stanic
2006-07-06  7:02     ` Richard Downing
2006-09-21  5:59 Zachary Kotlarek
2006-09-21 13:57 ` Richard Downing

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20060630092759.27727.qmail@c80d5cd64668b0.315fe32.mid.smarden.org \
    --to=pape@smarden.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).