Furthemore, these log entries seem to be courtesy of the session init itself (so, the output of upstart) and running init with -q does not suppress the messages. So yeah, this is an upstart bug after all.
Furthemore, these log entries seem to be courtesy of the session init itself (so, the output of upstart) and running init with -q does not suppress the messages. So yeah, this is an upstart bug after all.