Useless syslogd
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...
This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 5 lines · Gary Thomas
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
Quoted 9 lines
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
I think 'logread' is hooked up to read from the buffer, but it seems to be broken at the moment...
Tom
Quoted 10 lines · Tom Zanussi
Quoted 9 lines · Gary Thomas
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...
Quoted 8 lines
Quoted 5 lines
This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
I think 'logread' is hooked up to read from the buffer, but it seems to be broken at the moment...
Thanks for pointing this out. It does seem to work (minimal test), but I still prefer a file, especially since the buffer mode seems to use a circular buffer that could get overwritten.
At least I have an easy way to define my own config file.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 10 lines · Tom Zanussi
Quoted 9 lines · Gary Thomas
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...
Quoted 8 lines
Quoted 5 lines
This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
I think 'logread' is hooked up to read from the buffer, but it seems to be broken at the moment...
logread is indeed the way to access the circular buffer, though it does seem like operating against a file would be more consistent -- I think the original logic was that most of the targeted devices didn't have a writable area to put the logs, other than flash, if that, but using tmpfs seems just as good a solution and the logs can be read in a more traditional fashion..
Signature · 5 lines
Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
Quoted 20 lines · Chris Larson
Quoted 10 lines · Tom Zanussi
Quoted 9 lines · Gary Thomas
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...Quoted 8 lines
Quoted 5 lines
This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
I think 'logread' is hooked up to read from the buffer, but it seems to be broken at the moment...
Quoted 6 lines
logread is indeed the way to access the circular buffer, though it does seem like operating against a file would be more consistent -- I think the original logic was that most of the targeted devices didn't have a writable area to put the logs, other than flash, if that, but using tmpfs seems just as good a solution and the logs can be read in a more traditional fashion..
Indeed. I hacked it before(*) so that /var/log could be ramdisk and then rotate the logs to FLASH periodically. Sadly, this isn't supported out of the box (at least busybox's logrotate insists on keeping the rotated files in /var/log), but I think it's the best of both worlds.
(*) using an ad-hoc logrotate that could have the rotated files end up in a directory other than /var/log
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 29 lines · Gary Thomas
Quoted 21 lines · Chris Larson
Quoted 10 lines · Tom Zanussi
Quoted 9 lines · Gary Thomas
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...Quoted 8 lines
Quoted 5 lines
This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
I think 'logread' is hooked up to read from the buffer, but it seems to be broken at the moment...
Quoted 6 lines
logread is indeed the way to access the circular buffer, though it does seem like operating against a file would be more consistent -- I think the original logic was that most of the targeted devices didn't have a writable area to put the logs, other than flash, if that, but using tmpfs seems just as good a solution and the logs can be read in a more traditional fashion..
Quoted 9 lines
Indeed. I hacked it
before(*)so that/var/logcould be ramdisk and then rotate the logs to FLASH periodically. Sadly, this isn't supported out of the box (at least busybox's logrotate insists on keeping the rotated files in/var/log), but I think it's the best of both worlds.(*) using an ad-hoc logrotate that could have the rotated files end up in a directory other than
/var/log
I think this is a good idea, but I don't know that anyone will have the time to jump on it right now. May I suggest you open a bug / feature enhancement so we don't lose track of this?
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 36 lines · Darren Hart
Quoted 35 lines · Gary Thomas
Quoted 21 lines · Chris Larson
Quoted 10 lines · Tom Zanussi
Quoted 9 lines · Gary Thomas
... at least out of the box.
It seems that syslog is configured to store its messages in a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf DESTINATION="buffer" # log destinations (buffer file remote) ...Quoted 8 lines
Quoted 5 lines
This doesn't seem very useful to me. I know I can override this in my platform recipes, but I was just wondering what's the rationale? Would it not make more sense to chose DESTINATION="file"? Otherwise, where do the messages go? How can I see them?
I think 'logread' is hooked up to read from the buffer, but it seems to be broken at the moment...
Quoted 6 lines
logread is indeed the way to access the circular buffer, though it does seem like operating against a file would be more consistent -- I think the original logic was that most of the targeted devices didn't have a writable area to put the logs, other than flash, if that, but using tmpfs seems just as good a solution and the logs can be read in a more traditional fashion..
Indeed. I hacked it
before(*)so that/var/logcould be ramdisk and then rotate the logs to FLASH periodically. Sadly, this isn't supported out of the box (at least busybox's logrotate insists on keeping the rotated files in/var/log), but I think it's the best of both worlds.
Quoted 6 lines
Quoted 3 lines
(*) using an ad-hoc logrotate that could have the rotated files end up in a directory other than
/var/logI think this is a good idea, but I don't know that anyone will have the time to jump on it right now. May I suggest you open a bug / feature enhancement so we don't lose track of this?
Done as two separate bugs
Bug 717 - Improve syslog configurability
Bug 718 - Allow logrotate to use a different file system from the original logs
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------