Comment 7 for bug 1021293

I've caught this in the act with strace, but the log is 2GB and will take some time to analyse.

My best guess is that one of the packages upgraded in this run starts a daemon which fails to disconnect itself from the stdout/stderr it's given on startup. That means log-output never exits because the file descriptors it's watching are still open. If this theory is correct, then a fix would be twofold: in quantal, fix the daemon to disconnect properly; in both precise and quantal, extend the no-op SIGCHLD handler hack in log-output to force it to exit as soon as its child process exits, even if --pass-stdout isn't being used.