On Tue, Apr 24, 2012 at 11:27 AM, Tomasz Czapiewski <xe...@irc.pl> wrote:
> Looks like the problem was caused by this commit:
> 7449e18190b8ed07a7cd1711b40885ae4b97efb4
> ('getty,login: tighten up handling of ctty, pgrp, and tty attr restoring on
> timeout')
>
> Tested on x86_64 and mipsel.
>
> Regards,
> Tomasz Czapiewski
>
> ---------- Forwarded message ----------
> Date: Mon, 23 Apr 2012 23:26:27 +0200 (CEST)
> From: Tomasz Czapiewski <xe...@irc.pl>
> To: busybox@busybox.net
> Subject: [1.20.0] getty: setsid: Operation not permitted
>
> Hi,
> I'm getting "getty: setsid: Operation not permitted" error after BusyBox
> upgrade from 1.19.3 to 1.20.0 - config is rather the same, besides new
> defaults (both configs attached).
>
> dmesg:
> Mon Apr 23 23:16:57 2012: process '/sbin/getty -L ttyS0 115200 vt102' (pid
> 909) exited. Scheduling for restart.
>
> I'm also getting "getty: setsid: Operation not permitted" when trying to run
> above command from shell.It means that setsid fails. We used to just assume it always succeeds. Which was wrong. For one, successful setsid drops ctty, but failing one does not. setsid fails if getty is started in a way so that it is a process leader, but not a session leader. For one, this is what happens when you run a single command (not a pipe) from interactive shell: it is made a process leader by the shell. That's why getty from interactive shell doesn't work (and probably is not expected to). How do you start your getty? From init? Which init - busybox's? -- vda _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
