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.
>You reverted the culprit commit and then the behaviour was as expected/known? - Sedat - > 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. > > Regards, > Tomasz Czapiewski > _______________________________________________ > busybox mailing list > busybox@busybox.net > http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
