Comment 1 for bug 348346

10:23 < lool> Keybuk: I think my init just became somewhat broken on armel
              after today's upgrade; it's not respawning gettys anymore
10:23 < lool> The only thing in daemon.log is:
10:23 < lool> Mar 25 09:00:52 babbage init: Re-executing /sbin/init
10:24 < lool> In syslog I also see immediately thereafter:
10:24 < lool> Mar 25 09:06:49 babbage kernel: [159660.980000] udev: starting
              version 140
10:26 < lool> PID 1 is in: select(7, [3 5 6], [], [], NULL
10:41 < lool> It seems it's the libc6 upgrade triggering the restart of
              init/upstart
10:47 < lool> Keybuk: This happened on my two armel installs
10:48 < seb128> lool: today's upgrade should be pretty non-update since we are
                frozen for beta no?
10:48 < lool> Keybuk: I did a "touch /etc/event.d/ttyS0", this made upstart go
              out of the select, scan the file again, but it didn't respawn the
              getty
10:49 < lool> seb128: I think the bug was there before beta, but any libc
              update which runs "init u" will have triggered it, and there was
              a libc update just before beta freeze (last friday)
10:49 < lool> I'm only upgrading now
10:50 < lool> seb128: But right, it's the upgrade which I ran today, not from
              the updates the archive got today, thanks for clarifying
10:50 < lool> running "init u" manually has a larger effect, but still doesn't
              respawn; /me reboots

(Confirmed after a reboot that "init u" still breaks)