[BusyBox] TAKE 2: Message on Startup: "sh: can't access tty; job control turned off"
Stewart Brodie
stewart.brodie at pace.co.uk
Wed Jan 8 10:53:04 UTC 2003
In message <3E1C643E.276BE10 at simtreas.ru>
"Vladimir N. Oleynik" <dzo at simtreas.ru> wrote:
> Stewart,
>
> > [snipped patch that added ioctl(0, TIOCSCTTY, 0); to init.c]
> >
> > That doesn't work for me with my serial console: I get back -1/EPERM.
> >
> > Implicitly, the device_open call just after the setsid() would normally
> > make the opened device the controlling terminal - which looks to have
> > happened based on getting EPERM back. Did you mean to pass 1 as the
> > final parameter to ioctl? Putting it in with 1 as the third parameter
> > instead makes the message go away. Which is odd, because that implies
> > that there is already a
>
> Hmm. Interesting. Have you syslog? If have, what giving messages: "Starting
> pid %d, console %s: '%s'\n", getpid(), a->terminal, cmdpath);
>
> /dev/console or /dev/ttySN?
It reports /dev/console
--
Stewart Brodie, Senior Software Engineer Cambridge CVS administration team
Pace Micro Technology PLC
645 Newmarket Road
Cambridge, CB5 8PB, United Kingdom WWW: http://www.pacemicro.com/
More information about the busybox
mailing list