Upstart jobs that don't start daemons should all be marked with the "task" keyword.  However, this needs to be done carefully because marking job X as task changes the behavior of "start on started X" in the following way: for a task, "started X" fires when the process started by exec or script ends.  For a non-task, "started X" fires when that process has started.  Getting this wrong can create race conditions.

Some jobs that should probably be marked as tasks are: swap.conf, crash-boot-collect.conf.  There are many others, and most of them are probably not referenced by other jobs, so it makes no difference whether they are tasks or not.  Still, there could be bugs lurking in there.

OK maybe this is a weenie bug but I have already typed it in, so here it goes.