[BusyBox] TAKE 2: Message on Startup: "sh: can't access tty; job control turned off"
Vladimir N. Oleynik
dzo at simtreas.ru
Wed Jan 8 10:50:05 UTC 2003
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?
--w
vodz
More information about the busybox
mailing list