Comment 81 for bug 969489
Revision history for this message
| Clint Byrum (clint-fewbar) wrote Re: [Bug 969489] Re: lightdm tries (and fails) to start too early? | #81 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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://
> "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?