Upstart only gained the ability to re-exec statefully in Raring. The man page for telinit on Lucid explains that state is not preserved and also warns that running this command is not recommended.
Note that upstart has to re-exec itself on Lucid if certain key packages are upgraded to ensure a clean filesystem unmount. However, to minimise issues, the re-exec only occurs at shutdown after all jobs have stopped. In summary: do not run 'telinit u' manually as the man page warns. ** Changed in: upstart (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1374610 Title: telinit u makes upstart's /sbin/init lose all information on running processes (PIDs) Status in “upstart” package in Ubuntu: Won't Fix Bug description: running telinit u causes init to re-exec itself. It loses all process state information in the process, so that services can no longer be stopped/restarted, and restart or start will either start a daemon twice or fail to start it as a consequence. There needs to be a way that either: - init, telinit, initctl and possibly other manual pages warn of this loss of information; or - this feature gets removed, or - init remembers the process IDs across a restart unless told otherwise. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: upstart 0.6.5-8 ProcVersionSignature: Ubuntu 2.6.32-65.131-generic-pae 2.6.32.63+drm33.26 Uname: Linux 2.6.32-65-generic-pae i686 Architecture: i386 Date: Fri Sep 26 21:35:01 2014 SourcePackage: upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1374610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp