Comment 63 for bug 98955
Revision history for this message
| Charles Atkinson (7-launchpad-catcons-co-uk) wrote | #63 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hello (especially Sergei) :-)
I'm trying to go further, running bootlogd on ubuntu 8.04.02 running in a VirtualBox virtual machine with / mounted read-only and a writeable /var/log mounted later. Isn't it always the way -- the code works perfectly well and then someone shifts the goal posts?!
I do understand that I am on my own here and Sergei has said he is not supporting this "as is" version of bootlogd but a couple of pointers would help and I am happy to feed back my adventures in case anyone else is crazy enough to want to do the same thing.
Reviewing the code, the read-only / and a writeable /var/log appearing later should work OK -- if I understand the code correctly -- but it doesn't. bootlogd does start during boot but there's no /var/log/bootmsg file after booting.
A long time ago I was a fluent applications (not kernel) C programmer but it's rusty now so please allow for some ignorance.
In bootlogd.c, there is a while loop starting at line 585 and ending at line 664. Each iteration it reads from the intercepted console output, writes what it gets to the console and either buffers it or writes it to logfile. What is the access() function on line 643? Lines 648 and 651 try to open logfile in append mode, creating it if it does not exist. As I understand it this should fail until there is a writeable /var/log directory. If that is correct then it should work ... ?
Best
Charles