=== Md_ is now known as Md
[07:14] <xzirrow> Does anybody can help me with upstart to get /var/log/boot and my boot-up messages ?
[08:30] <keesj> try the kernel boot you can get with the dmesg command but there is no such logging facilitie in upstart
[08:37] <xzirrow> too pity. Yes i can see kernel messages in dmesg - i'm interested in messages of phase two :)
[08:38] <xzirrow> is it planned to realise such thing in future ?
[08:50] <keesj> upstart itself logs events to syslog and you can (apparently) log the output of the processes to syslog
[08:50] <keesj> after that is's a matter of configuring syslog to log to the right file I guess
[08:51] <xzirrow> Do I need configure smth in upstart to make it log starting scripts output to syslog ?
[08:52] <keesj> I don't know the future of upstart and I am not developing in the main branhc
[09:14] <xzirrow> Do I need to config smth in upstart to make it log messages from startings scripts to syslog ?
[09:15] <Keybuk> Upstart doesn't do that
[09:16] <keesj> http://upstart.ubuntu.com/wiki/Stanzas check the "console"
[09:16] <keesj> apparently it's called "logger"
[09:17] <Keybuk> that'd been disabled for ages
[09:17] <keesj> Ok , sorry about that
[09:38] <xzirrow> So, as i can get - there is no possible way to recive /var/log/boot ?
[10:03] <Keybuk> xzirrow: not currently
[10:08] <xzirrow> Keybuk, so console output or console logged at ( /etc/event.d/logd) does nothing with upstart ?
[10:10] <Keybuk> console output will send the output to the console
[10:32] <xzirrow> Keybuk, so console logged will do what ? 
[10:34] <Keybuk> nothing
[10:34] <Keybuk> it's not implemented right now
[11:01] <xzirrow> Keybuk, ok, thank you very much - it clearified situation
[11:02] <Keybuk> I'd like to do something with it, obviously
[11:02] <Keybuk> but there's lots of problems and pitfalls
[11:02] <Keybuk> a miriad of different syslog daemons
[11:02] <Keybuk> I'd kinda like cron "mail output on failure" functionality
[11:02] <Keybuk> and the filesystem is generally read-only for much of the boot
[11:14] <keesj> tricky, what the kernel does is to use a ring buffer for the kernel output
[11:15] <Keybuk> an ordinary growing buffer would probably do just as well
[11:17] <keesj> I also guess you wil need to add some instance information, and that kinds a sounds like syslog again
[11:17] <keesj> in our setup we have the busybox syslog logging to memory with a shared buffer , you can then read the data using logread
[11:18] <keesj> (but no job output indeed)
[11:19] <Keybuk> "some instance information" ?
[11:45] <keesj> what job instance is generating the output
=== damjan_ is now known as damjan
[17:28] <ion_> http://www.networkworld.com/community/node/39858