[10:48] <sveinse> I'm trying to get two services up and running on a Natty system and I have some dependency issues:
[10:49] <sveinse> job 'a' is set to start on (local-filesystems and starting network). Its a task.
[10:50] <sveinse> job 'b' is set to start on ( runlevel [2] and stopped a ), also a task. But it seems this job is never run.
[10:50] <sveinse> Is there a problem using and statements like this for job b ?
[19:56] <lucs> Hi.
[19:57] <lucs> Does the upstart syntax support continuation lines, like with a \ at the end of a line?
[20:01] <lucs> I could try it and see, but maybe I can avoid a reboot or two if I know whether it's supposed to work or not :)
[20:10] <SpamapS> lucs: you don't have to reboot to run 'start jobname' ;)
[20:11] <lucs> True, but I've had trouble fixing broken scripts in the past (required rebooting to get the machine in a clean state).
[20:12] <lucs> SpamapS: By the way, do you happen to know if contiuations with \ are supported? :)
[20:12] <SpamapS> do not know no
[20:12] <lucs> Ah, okay.
[20:13] <SpamapS> I would assume yes in side script/end_script
[20:13] <lucs> I guess I'll just try it (but only later).
[21:27] <JanC> lucs: line breaks are allowed within parentheses
[21:28] <JanC> e.g. within parentheses in start on / stop on stanzas
[21:29] <JanC> but AFAIK no "\" at the end of a line
[21:42] <lucs> JanC: I was thinking within "script/end script", to make some of the longer lines easier to read.
[21:42] <lucs> Oh well.
[21:43] <JanC> ah
[21:44] <JanC> lucs: that might work actually, if /bin/sh supports it?
[21:45] <JanC> I'm not 100% sure how things get forwarded
[21:47] <JanC> but the docs seem to indicate that everything between "script" and "end script" gets passed to /bin/sh
[22:34] <lucs> JanC: Then I'm certainly going to try it :)
[22:34] <lucs> Thanks.