Bash completion for upstart

Michael Biebl mbiebl at gmail.com
Sat May 19 05:26:24 BST 2007


2007/5/18, Scott James Remnant <scott at netsplit.com>:
> On Thu, 2007-05-03 at 12:16 +0200, Michael Biebl wrote:
>
> > 2007/5/3, Alex Smith <alex at alex-smith.me.uk>:
> > > Michael Biebl wrote:
> > > >
> > > > I could make the start/stop completion more sophisticated, and only
> > > > list the running jobs for stop and the stopped jobs for start. Do you
> > > > think this would be a good feature?
> > >
> > > Yes, I think that would be good.
> >
> > Ok, updated script is attached. Though it is rather slow for stop/status.
> > Somehow, "initctl list" can be quite slow from time to time.
> >
> This would be worth debugging, since initctl shouldn't be slow at all.
> This could be a performance issue inside upstart itself.

I've run "initctl list" a hundred times and measured the execution via
time. Attached is a log.
As you can see, sometimes (~ 1 out of 3) I get spikes of 0.3 sec,
which is definitely noticeable as lag.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: upstart.log
Type: text/x-log
Size: 4286 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20070519/1f0e7760/attachment.bin 


More information about the upstart-devel mailing list