thaper | I am trying to start upstart from /init and it works but it runs in the foreground and i have no console ... any help is appreciated | 14:41 |
---|---|---|
thaper | exec upstart 3 | 14:41 |
thaper | is the last command in /init | 14:42 |
thaper | well i do have a console but is controlled by upstart so it just has upstart messages if i use exec /sbin/init --debug 3 | 14:43 |
thaper | last command in /init is "exec /sbin/init --debug 3 | 14:44 |
thaper | using ubuntu 9.10 | 14:45 |
thaper | right .,.. so i get a console when i ssh into machine and "initctl start tty1". So, why doesnt that just start when i "exec /sbin/init 3" ? | 15:10 |
sadmac2 | thaper: what's in your tty job definition? | 15:12 |
thaper | 1 sec | 15:16 |
thaper | respawn | 15:17 |
thaper | exec /sbin/getty -8 38400 tty1 | 15:17 |
thaper | start on stopped rc RUNLEVEL=[2345] | 15:18 |
thaper | stop on runlevel [!2345] | 15:18 |
thaper | not in that order | 15:18 |
thaper | i didnt change the tty job definition at all | 15:19 |
sadmac2 | which did you change? | 15:19 |
thaper | none | 15:20 |
thaper | i didnt change any of them | 15:20 |
thaper | I am just running "exec /sbin/init 3" from /init ... it is the last command | 15:21 |
thaper | when i ssh into the machine ... "initctl list" shows all jobs "stop/waiting" | 15:22 |
thaper | when i "initctl start tty1" a login prompt apears on the machine | 15:24 |
sadmac2 | idk what /init is | 15:24 |
sadmac2 | this is likely a distro-specific question, in which case it would be inappropriate for this channel anyway | 15:25 |
thaper | it is just a script | 15:25 |
thaper | that runs a few commands that need to be run before /sbin/init | 15:26 |
thaper | the kernel jumps there before /sbin/init | 15:26 |
thaper | so i start /sbin/init as the last command in /init | 15:26 |
sadmac2 | this likely has a lot to do with your distro's deployment of upstart and not upstart proper, and also doesn't sound like the right way of doing whatever it is you're trying to do. | 15:27 |
thaper | hmmmmmm it works fine with the sysvinit... | 15:28 |
thaper | it works with gentoo sysvuinit | 15:28 |
thaper | i need to get this working because i want to run it on any distro that uses upstart | 15:29 |
thaper | thank you fr your hep though | 15:29 |
thaper | help | 15:29 |
thaper | heheheeh | 15:29 |
thaper | what is upstart proper ? | 15:30 |
thaper | that i would like to know | 15:30 |
thaper | do you have a link ? | 15:30 |
thaper | thanks sadmac2 | 15:30 |
thaper | well i looked into the source and if upstart is not pid1 then telinit runs and then upstart becomes pid1 so there should be no problem with starting /sbin/init from a script | 15:33 |
thaper | wonder why it hangs though | 15:33 |
thaper | thanks sadmac2 fixed with "start on startup" in tty1.conf | 16:13 |
Keybuk | mbiebl: are you going to Debconf? | 18:11 |
Keybuk | JanC: are you? | 18:11 |
mbiebl | Keybuk: probably not | 18:12 |
=== sadmac2_ is now known as sadmac | ||
sadmac | been too long since I conference'd. Hopefully I'll make it to FUDCon F14 | 18:30 |
Keybuk | TOMCAT! | 18:31 |
sadmac | Keybuk: wtf is tomcat? | 18:31 |
Keybuk | an F-14 | 18:31 |
sadmac | Keybuk: or a Java app server (*shudder*). What are you getting at? | 18:32 |
Keybuk | I'm just amused that Fedora release numbering now co-incides with US Air Force plane designations | 18:33 |
Keybuk | clearly F14 has to have some Top Gun inspired codename | 18:33 |
Keybuk | Fedora 14 "Maverick" or something | 18:33 |
sadmac | Keybuk: none of the clever ones like that seem to get through the naming process | 18:35 |
sadmac | Keybuk: We really wanted 11's code name to be "goes to" | 18:35 |
mbiebl | Keybuk: I'm running a copy of the latest lucid bits on an older laptop | 19:03 |
mbiebl | And during boot I get those kernel messages | 19:04 |
mbiebl | http://paste.debian.net/66811/ | 19:04 |
mbiebl | Disk access is pretty slow | 19:04 |
mbiebl | When I disable ureadahead it seems I can't reproduc these problems | 19:05 |
Keybuk | no idea on that one | 19:05 |
Keybuk | all ureadahead does is trace or read | 19:05 |
mbiebl | I'm not sure if it is really ureadahead or just some weird side effect | 19:06 |
mbiebl | But I never see those problems on my Debian installation | 19:06 |
sadmac | I hate disks | 19:07 |
mbiebl | I was scared pretty bad when I noticed that, thought my harddisk is dying | 19:07 |
mbiebl | Keybuk: just found this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892 | 19:09 |
mbiebl | so it's most likely not an ureadahead bug :-) | 19:09 |
mbiebl | And I do have as SAMSUNG drive | 19:12 |
sadmac | cscope may have the worst UI ever | 19:13 |
sadmac | Keybuk: could I get your thoughts on nih_error's design? had some quick ideas for improvement and wanted to make sure I hadn't missed anything important | 20:17 |
Keybuk | let me know your thoughts first ;) | 20:20 |
Keybuk | the only real aim I had was | 20:20 |
Keybuk | - you shouldn't need to initialise an error to catch one | 20:20 |
Keybuk | - you shouldn't need to pass something to a function to get an error back | 20:20 |
Keybuk | - errors should be switch() able | 20:20 |
sadmac | Keybuk: well, first there's your documentation assertion that you must check the return value of the function to determine if an error was raised. | 20:22 |
sadmac | Keybuk: a design where you might "check" whether an error was raised introduces its own problems (or at least temptations to create them) | 20:22 |
sadmac | Keybuk: I actually like a rather radical alternate assertion: Return value is UNDEFINED if an error was raised. | 20:23 |
Keybuk | then you can't do | 20:24 |
Keybuk | if (! function_call (..)) | 20:24 |
Keybuk | { | 20:24 |
Keybuk | /* handle error */ | 20:24 |
Keybuk | } | 20:24 |
sadmac | Keybuk: no, you're forced to do: | 20:25 |
sadmac | foo = function_call (..) | 20:25 |
sadmac | if (got_error) | 20:25 |
sadmac | ... | 20:25 |
sadmac | Keybuk: but there's more evil I have in store | 20:25 |
sadmac | Keybuk: I'd like to be able to do something like this: | 20:26 |
sadmac | nihe_(function_call (...)) | 20:26 |
sadmac | /* go on ignoring errors */ | 20:26 |
sadmac | where nihe_ is a macro that would do: | 20:26 |
sadmac | ({ ret = function_call (..); | 20:27 |
sadmac | if (got_error) | 20:27 |
sadmac | return /* return is undefined, so stuff something here to shut up GCC */ | 20:27 |
sadmac | ret; }) | 20:27 |
sadmac | Keybuk: thereby giving us most of try/catch without any stack tricks whatsoever. | 20:28 |
sadmac | Keybuk: nih_local still works, etc. | 20:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!