Excerpts from Ivo Anjo's message of 2013-07-22 16:39:16 UTC: > > I have not seen data that proves it has 0 bad effects. I'd suspect that > > it would have a minor impact on time between power-on and login for > > those users who are not affected, but I also have no data on that either. > > Sorry... say what!? I will just quote it for you, from canonical's upstart > documentation: > http://upstart.ubuntu.com/cookbook/#respawn > "6.26 respawn > Without this stanza, a job that exits quietly transitions into the > stop/waiting state, no matter how it exited. > With this stanza, whenever the main script/exec exits, without the goal of > the job having been changed to stop, the job will be started again." > > So please don't make up suppositions and compare them to facts. >
Ease up, we're all working together right? Respawn is a mitigation strategy and I actually thought that was in the file already. Good idea to just add it, though it will fail to help if it respawns too fast. The workaround I thought you were referring to was changing the "start on". Perhaps open a second bug, reference this one, and submit a patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
