bind to multiple sockets #17

New issue

Open

opened 2019-03-25 01:41:22 +01:00 by boyska · 3 comments

boyska commented

2019-03-25 01:41:22 +01:00

Owner

binding multiple sockets can be useful. an example is being able to receive messages from journald (which requires binding a specific path) but also from a classical udp port.

implementation-wise, -syslogd-socket should be an array of strings

binding multiple sockets can be useful. an example is being able to receive messages from journald (which requires binding a specific path) but also from a classical udp port. implementation-wise, -syslogd-socket should be an array of strings

boyska commented

2019-03-25 02:00:34 +01:00

Author

Owner

plus: being able to bind to systemd-activated sockets would be great!

here is some doc: https://vincent.bernat.ch/en/blog/2018-systemd-golang-socket-activation

plus: being able to bind to systemd-activated sockets would be great! here is some doc: https://vincent.bernat.ch/en/blog/2018-systemd-golang-socket-activation

boyska commented

2019-05-02 19:07:37 +02:00

Author

Owner

go-syslog doesn't seem to be very collaborative towards adding "custom" listeners: it doesn't have anything similar to a Serve method, so the operation of listening and serving are coupled.

However, we already forked go-syslog as part of #23, so we could improve it on this aspect, too. It shouldn't be so hard.

go-syslog doesn't seem to be very collaborative towards adding "custom" listeners: it doesn't have anything similar to a `Serve` method, so the operation of listening and serving are coupled. However, we already forked go-syslog as part of #23, so we could improve it on this aspect, too. It shouldn't be so hard.

boyska commented

2019-05-03 15:26:44 +02:00

Author

Owner

socket activation done in b0cd779 + f7caefd; the limitations of go-syslog have been fixed forking go-syslog even more.

The issue isn't fixed because the subject still needs to be addressed; however, work has been done that will make it easier to do it.

socket activation done in b0cd779 + f7caefd; the limitations of go-syslog have been fixed forking go-syslog even more. The issue isn't fixed because the subject still needs to be addressed; however, work has been done that will make it easier to do it.