From: Dan Melomedman <dan@a.mx.devonit.com>
Subject: Re: getty trouble
Date: Fri, 20 Aug 2004 12:45:07 -0400 [thread overview]
Message-ID: <20040820164507.GK30800@mail.devonit.com> (raw)
In-Reply-To: <20040820071950.11549.qmail@7e729926274f71.315fe32.mid.smarden.org>
Gerrit Pape wrote:
> On Thu, Aug 19, 2004 at 01:30:46PM -0400, Dan Melomedman wrote:
> > Hello. Thanks for runit, I love it.
> >
> > 'getty' runs fine. 'mingetty' refuses to run though, because it gets
> > EPERM on a tty open. Any ideas? mingetty used to run fine under SysV
> > init. This is RH 6.2, with the old getty and mingetty. Thanks.
>
> Most probably it's because runsv doesn't automatically make a service
> run script a process group leader. Some getties call setsid(2) on their
> own, some doesn't. For those which doesn't, you can use chpst(8) to
> change the process state.
>
> exec chpst -P mingetty ...
>
> Regards, Gerrit.
Could you please document this fact on the installation page? This issue
cost me a lot of time. Thanks.
--
"You can't manage a process intended to produce beautiful things without
knowing what beautiful is. American cars are ugly because American car
companies are run by people with bad taste." -Paul Graham
next prev parent reply other threads:[~2004-08-20 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 17:30 Dan Melomedman
2004-08-20 7:19 ` Gerrit Pape
2004-08-20 16:45 ` Dan Melomedman [this message]
2004-08-23 0:04 ` runsv and process groups (was Re: getty trouble) Charlie Brady
2004-08-23 13:26 ` runsv and process groups Clemens Fischer
2004-08-23 21:29 ` Charlie Brady
2004-08-26 16:27 ` Clemens Fischer
2004-08-26 17:05 ` Charlie Brady
2004-08-26 20:48 ` Gerrit Pape
2004-08-26 20:57 ` Paul Jarc
2004-08-29 9:39 ` Gerrit Pape
2004-08-27 1:06 ` Charlie Brady
2004-09-11 9:58 ` Gerrit Pape
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=20040820164507.GK30800@mail.devonit.com \
--to=dan@a.mx.devonit.com \
/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).