test: circolog binding to /dev/log #21

New issue

Closed

opened 2019-04-26 00:38:14 +02:00 by boyska · 2 comments

boyska commented

2019-04-26 00:38:14 +02:00

Owner

we should be able to be the "main" logger on the system. check if it is really possible, and document it

boyska commented

2019-04-26 01:23:04 +02:00

Author

Owner

binding to /dev/log kinda works, but I think there is some error involving message formats.

If I send messages with echo $RANDOM|logger (without any options), I have missing fields when I do circolog-tail.

If I use echo $RANDOM|logger --rfc5424, it works fine.

Debug should be done to determine:

where the error is (are we decoding a format as another format?)
if we can easily improve upon it

PS: of course you need to be sure there is nothing else on your /dev/log. On many systemd-based distro, this means

systemctl stop systemd-journal.service systemd-journal.socket systemd-journald-dev-log.socket
rm '/dev/log'

binding to `/dev/log` kinda works, but I think there is some error involving message formats. If I send messages with `echo $RANDOM|logger` (without any options), I have missing fields when I do `circolog-tail`. If I use `echo $RANDOM|logger --rfc5424`, it works fine. Debug should be done to determine: * where the error is (are we decoding a format as another format?) * if we can easily improve upon it PS: of course you need to be sure there is nothing else on your `/dev/log`. On many systemd-based distro, this means ```sh systemctl stop systemd-journal.service systemd-journal.socket systemd-journald-dev-log.socket rm '/dev/log' ```

boyska commented

2019-05-02 22:04:39 +02:00

Author

Owner

fixed together with #23