Scott James Remnant
scott at netsplit.com
Thu Nov 29 20:57:05 GMT 2007
On Thu, 2007-11-29 at 21:32 +0100, Mildred wrote:
> Le Mon 26/11/2007 à 23:43 Scott James Remnant à écrit:
> > Upstart, in the extraordinarily unlikely circumstance that it might
> > crash (0.3.8 hasn't had a single report of one in the 1 year+ it's
> > been out), simply forks and dumps core in the child -- thus
> > generating a useful core file. Ubuntu's apport hook will catch this
> > and ask the user if they'd like to file a bug report.
> Well, once I found a bug but never reported it since it was more my
> fault than upstart's. In fact I made upstart enter an infinite loop,
> thus eating 100% of my CPU. No other choice to restart.
> It was in fact a service that contained:
> start on starting
> start on started
> start on stopping
> start on stopped
> The purpose of this service was to print on the console little
> information about what was going on. But This service starting would
> make itself start again ... indefinitely.
> Perhaps it could be useful to detect such cases.
This should already be detected and kit the respawn limit.
What was the exact service? What version of Upstart?
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20071129/cb8b455c/attachment.pgp
More information about the upstart-devel