=== ion_ is now known as ion === JanC_ is now known as JanC [09:09] how about Keybuk ? :) === apw` is now known as apw [11:49] where does upstart not print the process ID in few cases ? [11:50] s/where/why/ [11:53] process id with exec lines and no process id with script lines ? [12:28] It always tells the pid it’s tracking. [12:29] what do you mean ion ? [12:33] sysconfig-middle start/running [12:33] gconfd start/running, process 438 [12:33] I have got lines like this, one of them with no PID. [12:44] sysconfig-middle probably has no main process. [12:45] how can that be ? [12:46] some main process should be in any case, at least I thought that way :o [12:46] Nope, it’s optional. [12:47] I thought a tool is run from script section or with exec. [12:47] and there is a main process in both cases. [12:47] yes [12:47] I am confused then :-S [12:48] What other way is there ? [12:48] script/exec is optional. [12:48] is, but both have main process. [12:52] My another issue is that when I try to enable the "--verbose" boot command-line option then I do not get this kind of messages (we discussed on Friday): Jan 14 14:52:49 deathspank init: tty6 main process (8557). [12:54] sysconfig-middle doesn’t seem to have a main process, judging from the fact that what you pasted from initctl status/list says so. [12:55] Try initctl log-priority [PRIORITY] [12:55] well, it should do the same like verbose. [12:55] "initctl log-priority warn" [13:00] but tried it out, did not help. [13:02] I definitely think what was run from a script section that does not have PID as said in the beginning. [13:06] but that is why they should have in warn, verbose mode a 'Jan 14 14:52:49 deathspank init: tty6 main process (8557)'-like entry which I do not have... [13:11] so it should show the PID of the shell, ttyS6 oslt. [13:22] for example: sysconfig-middle has a parent process and I would like to know that's PID. [13:23] * obviously has [14:41] any idea anybody, please ? [14:50] hi [14:51] I have a problem with upstart "stop" and "start" commands inside a 10.04 Vserver Guest [14:51] it seems it's the same problem outlined here [14:51] http://www.freak-search.com/de/thread/2643371/vserver_problems_installing_ubuntu_10.10_as_a_guest_of_a_debian_host [14:52] I have the same problem (ie stop "service" or start "service" hangs), this is the debug I get from "stop dbus" inside a ubuntu 10.04 guest: http://pastebin.com/AjA2sAKG [15:06] robs_: issues with upstart inside a vserver are a known problem [15:07] JanC: following http://linux-vserver.org/Upstart_issues the machine boots and halts just fine [15:07] JanC: only "start" and "stop" hang [15:10] I cannot believe I need to use audit or other kernellevel stuff directly to get the PID of the parent for a command that was run from the script field of upstart. [15:10] it just seems a bit khm.. :) [15:10] * upstart configuration file. [15:11] no idea why it cannot be the part of upstart :( [15:11] djszapi: are you sure the main script is still running? [15:12] how does that matter ? [15:12] syslog entry should be done when it runs ? [15:12] and upstart is not 1.0 yet, some features are still on the TODO list ;) [15:12] I know but I have been told on Friday it is possible with verbose cli boot parameter [15:13] and it seems that statement 1) was not true 2) I do somehing wrong [15:17] JanC: do you have any idea ? [15:18] Keybuk mentioned me on Friday: with verbose I should get like: Jan 14 14:52:49 deathspank init: tty6 main process (8557) in syslog [15:18] where tty6 is the 'sh' where the command was run from. [15:18] from the upstart config file's script entry. [15:39] btw, where is it the best to ask questions if this channel is not OK for that ? [15:40] djszapi: all the jobs I see with start/running and no PID are jobs that have no main exec/script, but only pre/post-start/stop [15:40] and this channel is fine for asking questions, alternatively you can try the mailing list [15:41] well I did not still get any answer. [15:41] from this morning. [15:42] the question is still the same, how can I get the process id of the parent ? [15:42] wherever it was run from, let it be pre/post-start/stop [15:43] are you sure it is still running? [15:44] I need the pid when it was running. [15:45] aegis-loader:191,sh:188,init:1 -> that is the call tree [15:45] and I would like to get 188 back. [15:45] aegis start/running [15:45] aegis.conf run the aegis-loader in a post-start like way [15:46] but I need to know the PID of the parent ('sh') [15:46] do you understand ? [15:46] yes ☺ [15:47] define "yes ?" :) [15:47] otherwise I would say 'yes'. [15:48] what you apparently see as a "?" was a smiley [15:48] pardon ? [15:48] yes, I understand what you want now [15:49] do you know the answer how to do it ? [15:49] verbose is supposed to do that. [15:49] also initctl log-priority warn [15:49] but none of them works :( [15:59] JanC: feel free to help me, if you can :P [16:09] djszapi: I did some test, and for me it lists pre-start shell PIDs ? [16:10] djszapi: maybe you don't need 'warn' but 'info'? [16:12] warn should only show warnings & errors? [16:13] JanC: verbose should work anyway. [16:13] but I am trying with info [16:14] 'debug' will show even more, but 'info' should be enough [16:15] does it work with 'warn' by you ? [16:16] no pid with info either. [16:17] JanC: http://pastebin.com/HVGiQHqz [16:18] which is supposed to be the PID of the 'sh' line ? [16:19] captrace lines are internal stuff, you can skip them, not that important tho. [16:28] http://pastebin.com/4CSGKYhm --> you can see the PID (13885) of the shell that executes the post-stop script (which only runs "sleep 10", hence it takes exactly 10 seconds to run) [16:30] that's with log-priority info [16:31] didn't test 'warn', but from the docs 'warn' shouldn't show this ;) [16:31] "`warn' (ordinary messages are suppressed whilst still logging warnings and errors);" [16:32] does your dbus job have any pre/post-stop scripts? [17:33] re [17:33] JanC: I do not really understand why you keep repeating this pre/post-start/stop thingy [17:33] it should return the PID of the parent in *any* case [18:12] djszapi: it seems like it currently doesn't log the PID of the shell indeed [18:12] in that case [18:13] you mean in my pastebin, right ? [18:13] not only in your pastebin, also on my system [18:14] that is a BUG [18:14] Scott mentioned it should. [18:49] JanC: what to do then ?