[10:05] does process handover work with current upstart bzr? (from an initramfs upstart to the "real" upstart) [10:20] no [10:36] what is missing? the ipc protocol between the two instances of upstart? [10:40] right [10:42] is it just that, or there needs to be any refactoring before this protocol is added? [10:43] the complete lack of any IPC is a major todo item right now [10:43] the necessary conf changes have already happened [10:45] I see. [10:50] a related, but not critical path, item is the atomicity of start & stop [10:51] they are not yet atomic? [10:53] I 'm setting a qemu image to play with boot-time facilities (upstart and grub2) [10:54] no [10:54] in the sense that: [10:54] start JOB with environment FOO=x BAR=y [10:54] this should start the job, storing those environment variables in it, and those environment variables should persist throughout the life of the job, including its stop scripts [10:54] if I now do [10:54] stop JOB [10:55] start JOB with environment FOO=y BAR=x [10:55] (immediately after each other - ie. restart) [10:55] the job should stop with FOO=x and BAR=y and not adjust its environment until it has completely stopped [10:56] I see, interesting [11:16] actually, it's turned out to be quite a headache [11:24] is "with environment" really needed? [11:24] (I guess it has to do with supporting different instances of a service right?) [11:33] right [11:33] and if you don't have environment, you don't know what event started you [11:34] right [11:37] and I guess I need service instances [11:39] instance cases are even more fun [11:39] since in theory, the environment attached is similar enough anyway [11:39] start getty TTY=tty1 [11:39] stop getty TTY=tty1 [11:39] start getty TTY=tty1 [11:39] doesn't really make much difference :) [11:44] and why is it such a problem for the atomicity? (I haven't looked at the source yet) [11:45] you are storing an event together with its environment, not? [11:51] I meant a job instance together with its environment [12:11] right [12:11] you'd need to store its current environment [12:11] and its next environment [12:12] or... [12:12] spawn a new instance, and don't let it start until the other stops [12:20] right, I see [12:57] I'm not sure which is the right solution === kylem_ is now known as kylem