=== j_ack [n=rudi@p508d84c1.dip0.t-ipconnect.de] has joined #upstart === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #upstart === Haitham [n=chatzill@82.114.170.175] has joined #upstart === Haitham [n=chatzill@82.114.170.175] has joined #upstart === Haitham [n=chatzill@82.114.170.175] has left #upstart [] === juergbi [n=juerg@80-219-17-127.dclient.hispeed.ch] has joined #upstart === Md_ [i=md@freenode/staff/md] has joined #upstart === Md_ is now known as Md === cortana [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk] has joined #upstart === j_ack [n=rudi@p508d9f93.dip0.t-ipconnect.de] has joined #upstart === AlexExtreme is now known as AlexExtreme[T] === AlexExtreme[T] is now known as AlexExtreme === rawler [n=ulrik@c-7b4ee155.98-2-64736c13.cust.bredbandsbolaget.se] has joined #upstart [08:36] heya ppl.. [08:37] i'm having a small issue, perhaps someone cold clarify a thing or two to me? [08:38] I've written a small startup-script that enables a vpn-connection and sets up a bridge as soon as internet-connection is up.. [08:38] however, when starting the service, the "start openvpn-dtvb" command hangs bootup until ctrl+c is pressed? [08:38] does anyone know anything about this? [08:41] http://pastebin.se/13022 <- the service-definition.. i can't figure what would block the startup.. [08:41] the service runs fine, btw.. the only problem is that I have to press ctrl+c to boot, which is a bit confusing.. ;) [08:44] <_ion> I don't immediately see what causes the problem, but on an unrelated note, what does Canal Digital have to do with a VPN? :-) [08:44] <_ion> That is, for what purpose do they provide it? [08:47] _ion: we don't.. ;) I work there, we use it for internal purposes.. :) [08:48] _ion: found the trouble myself.. I had to define it as a service (adding a line "service") [08:48] perhaps something that should be added to the FAQ? I could not find it in the documentation, but while browsing through gmane I found a similar problem.. [08:50] _ion: I see you're from Finland? [08:51] btw, forgot the ordinary, "great job".. really, great job with upstart.. :) kick-ass init-solution.. [08:52] when I first read about upstart I thought event-based seemed like a stupid idea, and were going for deps-based instead, but after working with it a little, as well as seeing the bigger picture, it's a killer.. :) [08:53] just the basic solution of beeing capable of things like triggering services based on particular interface-events is great.. [08:53] I can hardly wait for Feisty to get out, so that work on full integration for Feisty+1 can begin.. :) === Yorokobi [n=Yorokobi@ip67-88-113-150.z113-88-67.customer.algx.net] has joined #upstart [08:58] Is upstart's /sbin/init SELinux capable/compatible or should I use sysvinit for SELinux? (OS: Kubuntu Edgy, upstart ver: 0.2.7-7) [09:15] <_ion> rawler: Yeah, i'm from Finland. And d'oh, i should have realized the "service" stanza is needed. :-) [09:16] hehe.. it weren't when I wrote the service, about a year ago.. :) [09:16] _ion: btw, what's your role in Roundup? [09:16] <_ion> Roundup? [09:16] it's needed now after the JobsAsStates specification is implementaed afaik [09:17] *implemented === AlexExtreme hates this keyboard... [09:28] <_ion> yorokobi: I think there has been some discussion about SELinux on the mailing list, but i haven't paid much attention to it. [09:28] <_ion> yorokobi: Perhaps you'll find the answer from the archives. [09:28] _ion, yeah, I read through it [09:28] it looks like its still a work in progress [09:33] _ion: sorry.. Upstart.. doing a little too much at the same time now.. ;) [09:35] <_ion> rawler: Keybuk is the one who has done all the actual work. I'm mostly just an enthusiastic observer, trying to get an useful patch done every once in a while. [09:41] allright.. :) [09:41] just curious.. :) === Yorokobi [n=Yorokobi@ip67-88-113-150.z113-88-67.customer.algx.net] has left #upstart ["Bonum] === j_ack [n=rudi@p508d9f93.dip0.t-ipconnect.de] has joined #upstart