[00:34] <Keybuk> bootchart indicates those numbers are realistic
[00:34] <Keybuk> (boot is even longer with sreadahead if it goes in the background)
[02:50] <Justin___> Hi, I'm new to Ubuntu and (brand) new to upstart. I'm hoping to use upstart to launch a few shell scripts and I'm having a hard time
[02:50] <Justin___> Anyone on that could help me?
[02:57] <mbiebl> Justin___: just ask your questions 
[02:59] <Justin___> First of several. This script will work when I run it manually from console, but it isn't (apparently) launching at runlevel 2
[03:00] <Justin___> start on runlevel 2
[03:00] <Justin___> start on runlevel 3
[03:00] <Justin___> start on runlevel 4
[03:00] <Justin___> start on runlevel 5
[03:00] <Justin___> stop on runlevel 0
[03:00] <Justin___> stop on runlevel 1
[03:00] <Justin___> stop on runlevel 6
[03:00] <Justin___> script
[03:00] <Justin___>   cd /usr/share/atlassian/crowd
[03:00] <Justin___>   ./start_crowd.sh
[03:00] <Justin___> end script
[03:00] <mbiebl> Justin___: which upstart version do you use?
[03:01] <Justin___> 0.6.3
[03:02] <mbiebl> multiple start on stanzas are not allowed in upstart 0.6
[03:02] <mbiebl> use "start on runlevel [2345]"
[03:02] <mbiebl> stop on runlevel [016]
[03:02] <mbiebl> instead
[03:05] <Justin___> nice
[03:05] <Justin___> thanks
[03:08] <Justin___> Q #2: similar theme, but this one doesn't work automatically or manually (but it claims 'started' and gives a pid)
[03:08] <Justin___> description "Starts JIRA when the computer starts"
[03:08] <Justin___> start on runlevel [2345]
[03:08] <Justin___> stop on runlevel [!2345]
[03:08] <Justin___> script
[03:08] <Justin___> end script
[03:08] <Justin___> oops, got truncated
[03:09] <Justin___> description "Starts JIRA when the computer starts"
[03:09] <Justin___> start on runlevel [2345]
[03:09] <Justin___> stop on runlevel [!2345]
[03:09] <Justin___> script
[03:09] <Justin___> \/usr/share/atlassian/jira/bin/startup.sh
[03:09] <Justin___> end script
[03:20] <mbiebl> Justin___: if it's a one time task
[03:21] <mbiebl> add the "task" keyword
[03:21] <Justin___> It is, yeah. (it exits when done)
[03:21] <Justin___> then make a separate job for the analagous shutdown.sh? (with start on 01?)