/srv/irclogs.ubuntu.com/2007/05/21/#upstart.txt

quitte#define HAVE_SYS_INOTIFY_H 1 is in config.h. I'm out of ideas. maybe you can see a problem in the patch here: http://bugs.uclibc.org/view.php?id=917 ?12:27
Keybukyou need the functions in your uclibc as well as the headers12:47
quittethe kernel headers are in place,too. 12:55
Keybukyeah, you still need the stub functions though01:00
Keybukthe header declares the existance of the function, but not the function01:00
Keybukyou can probably just copy the syscall stuff into a header and inline it01:01
Keybuklike the nih/inotify.h thing does01:01
quittehmm. I hardly understood what you said. but I'll have a look at nih/inotify.h01:02
quitteok looking at it didn't give me any clue.01:06
=== mbiebl [n=michael@e180068028.adsl.alicedsl.de] has joined #upstart
=== Starting logfile irclogs/upstart.log
=== ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart
=== Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo
=== Topic (#upstart): set by Md at Sun May 6 19:59:46 2007
=== Md [i=md@freenode/staff/md] has joined #upstart
=== Keybuk [n=scott@quest.netsplit.com] has joined #upstart
=== juergbi [n=juerg@80-219-19-101.dclient.hispeed.ch] has joined #upstart
=== |Lupin| [n=seb@zen.loria.fr] has joined #upstart
|Lupin|Hello, everybody03:28
|Lupin|I am joinning the chan because it looks like upstart does not log the bot messages in /var/lob/boot, I am wondering why...03:30
=== tale [n=tale@207.235.54.1] has joined #upstart
Keybuk|Lupin|: we had some last-minute issues with logd03:47
Keybukit turns out that when it isn't running, processes that try to output to stdout die03:47
Keybukie. the shell running the shutdown scripts03:48
|Lupin|so ?03:51
|Lupin|Actually there is a file called /etc/event.d/logd03:52
|Lupin|it contains a line saying 03:52
|Lupin|console output03:52
|Lupin|Does one have to change this line to have hte output redirected to a file rather than to the console ?03:53
|Lupin|More in general, I can't find any documentation about the synta of the files under /etc/event.d03:53
Keybukthe console X line does indeed set where the input/output of a job goes; you set jobs to "console logged" to have them use logd, except this is disabled in the code03:55
Keybukthe lack of documentation is semi-deliberate, since the syntax isn't stable yet03:55
|Lupin|ok03:58
|Lupin|Keybuk: In fact what I would really like is to be able to have everything appearing on the screen at boot gathered in a file so that I can read it. Is this possible ?03:59
|Lupin|Or perhaps would it be more simple to switch back to sysvinit ?04:23
Keybukthere's various interesting ways to do that04:24
Keybukthe logd trick is to set the console to a set of sockets that are intercepted by a daemon04:25
Keybukthe disadvantage is obviously that without the daemon, the trick doesn't work04:25
Keybukan alternate trick is to use TIOCCONS to capture "console output"04:25
Keybukthe disadvantage to that is that you don't know which service is doing the output04:25
|Lupin|Keybuk: oh indeed the daemon is not installed...04:27
Keybuk(the other disadvantage to the logd trick is that with ordinary sockets, you don't have a tty, which can adjust the behaviour)04:27
|Lupin|Keybuk: I think I don't mind loosing the name of the service, as a temporary solution. But how can this solution be implemented, concretely, please ?04:27
Keybukthere's not an easy answer available right now04:28
|Lupin|Hmm...04:28
Keybukit turns out to be a more difficult problem04:28
|Lupin|If the system remains in text mode, will I be able to rean the console with shift-pagep / shift-page-down ?04:28
Keybukyes04:30
Keybukyou're obviously relying on the kernel ring-buffer size there04:31
=== wasabi_ [n=jhaltom@ubuntu/member/wasabi] has joined #upstart
|Lupin|yes04:34
|Lupin|I am wondering how I can keep the system in text mode.. ?04:35
|Lupin|is it a matter of runlevel ?04:37
|Lupin|I believed so, but runlevels 2, 3, 4 and 5 seem to run gdm... 04:49
Keybukremove gdm symlinks from one of the runlevels04:54
|Lupin|is it all I have to do ? okay.04:58
=== phoenix24 [n=phoenix2@59.176.11.215] has joined #upstart
|Lupin|it worked, thantks05:45
|Lupin|bye every body06:21
|Lupin|thanks a lot for your assistance06:21
=== |Lupin| [n=seb@zen.loria.fr] has left #upstart []
=== jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has joined #upstart
=== quitte [n=quitte@stgt-d9bebb70.pool.mediaWays.net] has joined #upstart
quittehi. is it possible that my problems compiling upstart using uclibc are related to the kernel being 2.6.13? that's the release that inotify was introduced.06:56
AlexExtremequitte, yes, you need a recent kernel06:56
quitte:( ok. so it'S impossible to use it on a fritzbox without loosing support for the proprietary modules06:56
KeybukUpstart works best when you have the most event support from the kernel06:56
Keybuksince if you're interested in an event-based init daemon, you're kinda inherently interested in the events to base it off06:57
Keybukthe kernel's uevent interface didn't reach maturity until about 2.6.1706:57
AlexExtremeyeah, it's better to have the uevent support for udev which was introduced in .17 IIRC06:57
quitteok i see. so i'd best stick with busybox init for now. maybe the vendor will update the kernel version someday, but i doubt it.06:58
=== cortana [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk] has joined #upstart
=== Starting logfile irclogs/upstart.log
=== ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart
=== Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo
=== Topic (#upstart): set by Md at Sun May 6 19:59:46 2007
=== Md [i=md@freenode/staff/md] has joined #upstart
=== jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has left #upstart []

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!