[Buildroot] [Bug 8746] New: At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[Buildroot] [Bug 8746] New: At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

            Bug ID: 8746
           Summary: At startup system stops with 'cannot set terminal
                    process group (-1): Inappropriate ioctl for device'
                    error
           Product: buildroot
           Version: 2015.11
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: rdbirt at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

After updating from buildroot 2015.02 I am seeing this error on system startup:

.
.
.
EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:1.
devtmpfs: mounted
Freeing unused kernel memory: 228K (c07db000 - c0814000)
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
sh-4.3# 

The same error occurs with 2016.02-rc2.  I am running this on a Wandboard quad
with kernel 3.18.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
Is this with our wandboard_defconfig or some kind of customization?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

--- Comment #2 from Ralph Birt <rdbirt@gmail.com> ---
Created attachment 6381
  --> https://bugs.busybox.net/attachment.cgi?id=6381&action=edit
buildroot 2016.02-rc2 config file

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

--- Comment #3 from Ralph Birt <rdbirt@gmail.com> ---
It's a custom config file.  Attached here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Your boot log shows that the kernel starts /bin/bash directly, but your
configuration shows that you're using systemd as the init system. So things
aren't matching really well here.

Are you booting with init=/bin/sh perhaps? If that's the case, then I believe
it's expected for bash (the shell chosen as the default one in your
configuration) to complain this way, because its standard input/output is
/dev/console.

See https://lists.gnu.org/archive/html/bug-bash/2013-10/msg00097.html for
example.

So, I believe this is not a bug in Buildroot, it is just a misconfiguration of
the system on your side.

Peter, what do you think?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

--- Comment #5 from Ralph Birt <rdbirt@gmail.com> ---
It seems that /sbin has been removed from 2015.11 and is, instead, made a link
to /usr/sbin.  So /sbin/init is now /usr/sbin/init.

I have an /sbin directory in my overlay skeleton directory structure so the
link to /usr/bin disappears and /sbin now contains just the few files I have
there, and those few files don't include /sbin/init.

The solution is for me to change my overlay directory structure so the files I
used to put into /sbin will now go into /usr/sbin.

Thanks for looking at this with me.

Regards,
Ralph

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8746

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|ASSIGNED                    |RESOLVED

--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Yes, since 2015.11, we have an option to merge /usr and /. From Buildroot's
CHANGES file:

        - Add support for /bin, /sbin and /lib to be symlinks to their
          corresponding directories in /usr. This is enforced for
          systemd configurations, and optional for other
          configurations.

As said above, this is mandatory for systemd (because systemd people expect
such a filesystem layout) and optional in other cases. Since you're using
systemd, this new organization has been automatically enabled.

I'll mark the patch as invalid then. Thanks for following up!

-- 
You are receiving this mail because:
You are on the CC list for the bug.