[09:42] Hi! Let me ask one question... [09:42] I'm preparing an upstart job that has to be executed on shutdown (or reboot). That job absolutely needs the network and local drives to be read-write accessible. [09:42] I can't find any "require network" instruction in upstart documentation. [09:43] After some tests, it seems to be ok with these access, but how could I be sure that those resources won't be shut down before or during my job to run? [09:43] It's running on Ubuntu 10.04LTS. [11:24] i use upstart in debian squeeze and wrote my own upstart script, but i always get: [11:25] Setting up test (0.1+2814M-1) ... [11:25] Usage: /lib/init/upstart-job {start|stop|restart|reload|force-reload} [11:25] insserv: warning: script 'test' missing LSB tags and overrides [11:25] insserv: Default-Start undefined, assuming empty start runlevel(s) for script `test' [11:25] insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `test' [11:25] any ideas how to fix this? [11:29] it's this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593348 [15:58] bancal: I suppose that job is a "task"? I think it should have "start on stopping networking RESULT=ok" or something like that (see "man 7 stopping") [15:58] Yes it's a task [15:58] I did : [15:59] start on starting rc RUNLEVEL=[06] [15:59] Which seems to work ... I can't be sure if it's guaranteed to work... [16:00] "start on stopping networking RESULT=ok" ... is that not to late in the shut down process? [16:00] yeah, probably not networking, but something about network filesystems [16:02] with your solution it will not run if you down the network for some other reason than shutdown, which is maybe what you want [16:16] Thanks for your interest, sorry but I really have to leave now (will be back tomorrow 8AM - switzerland) I keep it connected in case you want to write some more ...