[15:09] when i define a job like in http://pastebin.com/3ziQgxBT for shutdown (it works only for shutdown, which is intended), does this block, even if that script operation takes longer? [15:10] in the t1.sh script i did atm only a touch, but i want to run a service over the fs... [15:10] and if that does not block, the thing will not be completed, since it will take some time... [15:16] or should i rather use a pre-start script? [15:49] menace: you have some time, but eventually after timeouts it will be killed. [15:50] menace: what is that command doing? [15:50] scanning java libraries for viruses... stupid enterprise requirement >.< [15:50] menace: are you sure you can't do it earlier? this has potential to hold up files open on the filesystem, thus corrupting and requiring recovery on boot. [15:51] menace: if that is quick, than it should be fine. Otherwise, it's best to use cron to execute that. or user-session job instead, which can execute on logout for example. [15:52] if you can say a appropriate signal on upstart or dbus, which i could use? i have no idea which to use.. and upstart was rather easy to get [15:52] ah, user-session job, okay, i'll try that [18:02] a question: if my user-session-job is not complete, will the upstart system halt, until it is, or will it just shutdown? [18:42] menace: there is maximum delay, after which all processes are killed and system is shutdown. [18:42] menace: if you wish to inhibit shutdown, see dbus apis to notify about that. [18:43] i'm not sure, but it's something in gnomish* fredesktopish* things. [18:53] this seems like a complex issue o_O [18:55] at least, because i want the script started, if the user triggered shutdown, i then want to stop it and scan the directory [19:12] well.. since my target platform does not have systemd/logind (which is the inhibit thingie)... is there a configuration possibility to extend the upstart maximum delay? *desperated* [19:13] preferably without recompiling upstart? <.<