#21 test: circolog binding to /dev/log

Closed
opened 5 years ago by boyska · 2 comments
boyska commented 5 years ago

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

we should be able to be the "main" logger on the system. check if it is really possible, and document it
boyska commented 5 years ago
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 5 years ago
Owner

fixed together with #23

fixed together with #23
Sign in to join this conversation.
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.