[18:42] morning [18:45] heya. [18:47] how goes? [18:48] well. working with upstart for the first time. [18:49] does a concept equivilent to the status operation of an LSB init script exist in upstart currently? [18:51] hi Keybuk [18:51] Keybuk: upstart logging does not work ... [18:56] djszapi: it does, millions of people use it every day [18:56] it may not be working for you [18:56] I'm honestly starting to suspect somebody at Nokia has disabled that code in your source tree [18:57] nope [18:57] I made an own build today. [18:58] well, it works for me [18:58] perhaps you could tell me more about what doesn't work [18:58] what you've tried [18:58] etc. [18:58] it does not help me if you keep repeating it :) [18:59] it doesn't help you if you just say "nope" either ;-) [18:59] I just know it can work, thus it is worthwhile to try to fix it. [18:59] well "nope" is a kool word :P [18:59] btw, have you read my mail ? [18:59] I haven't read your mail [18:59] I do not know what else I could amend it with ... [19:00] ok [19:00] so you've patched upstart with my kmsg patch? [19:00] and that version of upstart is currently running as pid #1 ? [19:03] well, about. [19:03] "about" ? [19:04] yeah, the patch did not change anything to the previous statement, there are *NO* such messages anywhere. [19:04] right, I'm asking whether you have that version patched and running ;-) [19:04] ok [19:04] so let's try something [19:04] (as root) run the following [19:05] # initctl log-priority [19:05] it should print a word, what is that word? [19:06] FYI: I am @ home. [19:06] 21:06 pm [19:06] can you not access that box? [19:06] no VPN or anything? [19:06] to the prototype ? [19:06] no, I cannot. [19:06] ah [19:06] it is quite perfectly locked into the safe box. [19:06] what time of day can you usually access it? [19:06] while being there ? :) [19:07] what time? [19:07] no idea :) [19:07] haha, right [19:07] change day by day [19:07] really... [19:07] so what I'll do is reply to your mail with a sequence of debugging steps [19:07] if you could follow them exactly, and answer each of them when you have access to the box [19:07] then I should be able to figure out what's going wrong with it [19:08] well [19:08] please don't skip steps if you think you know the answer, the output I'm asking for is subtle and you might miss something that would tell me the problem [19:08] I can access to it in 11 hours [19:08] ok sure do not be afraid of that :) [19:08] yeah, in 11 hours I'll be going to bed [19:08] btw, we use 0.6.6 [19:09] with quilt patchset [19:09] where should I see kmsg logs ? [19:09] I tried the dmesg and the console where printk happens. [19:09] I actually have a hunch what's wrong [19:10] based on something somebody else at Nokia told me earlier this week ;-) [19:10] or go thorugh pls. [19:10] maybe I can answer for some of them [19:10] which can already show the mistake ... [19:10] well, first in your mail you say "warn" which actually means upstart will log *less*, you want log-priority info ;-) [19:10] somebody ? [19:10] me or other guy ? [19:10] yes [19:10] but I think in MeeGo you have an /sbin/init shell script wrapper for Upstart [19:11] I tried info [19:11] that was done [19:11] and that wrapper is not passing command-line arguments to Upstart [19:11] nothing changed regarding this [19:11] that is a typo in the mail, sorry. [19:11] right [19:11] I wanted to send a mail. [19:11] well, reply to my mail when you have the box, and follow the steps [19:11] I have just been at the school [19:11] and we'll chat tomorrow [19:11] "but I think in MeeGo you have an /sbin/init shell script wrapper for Upstart" -> why so ? [19:12] btw, ROTFL !!! :-) http://i.imgur.com/4kepL.jpg [19:12] djszapi: because someone else told me you do in the thread where I posted the kmsg patch [19:12] huh ? [19:12] not gotcha ... [19:13] it's ok [19:13] we'll pick this up tomorrow [19:13] highly doubt [19:13] hey ;-) I'm trying to help here [19:14] during your sleep ? [19:14] tomorrow my time [19:14] if yes, I am fine with that :) [19:14] ie. this time tomorrow once you've gone through the steps in my mail [19:14] well ... [19:14] when I will get to my box, you will be sleeping. [19:14] yes [19:14] so you reply to the mail [19:14] and then when I'm awake, I read the mail [19:15] and hopefully in the output of all the commands will be the clue that tells me what's wrong [19:15] well I have access to the srouce code. [19:15] * source [19:15] if I can help anything with that, do not hesitate to tell me ... [19:16] btw, I did see nowhere this --verbose option. [19:17] maybe it is just not documented ? [19:17] it's built-in to nih/option.c [19:17] odd I was thinking that it is kernel thingy ;) [19:17] no [19:17] it's an upstart thingy [19:18] Alright. [19:18] cya tmrw. [19:18] ty in advance. [19:18] (mail should be in your inbox now btw) [19:19] it is not. [19:19] just the thread ... [19:19] got. [19:20] haha I think all the output will be ok :) [19:20] I'm not looking for "ok" or not "ok" [19:20] (I am just kidding) [19:20] I'm looking for a clue that tells me what's wrong that you may miss [19:20] Upstart, like most software, uses different strings for the same states in different places [19:20] so by reading a log, as a developer, I can see what it's doing which isn't obvious to others [19:20] that is exactly what I meant with "ok", nothing is gonna inform you :) [19:21] okay, let us see and really thank you. [19:25] np :p