allow setting up unix named sockets for listening
When troubleshooting issues with our production syslog servers, its often not possible to deliberately duplicate discovered issues as it then affects production. Something which would be extremely useful in this case is if we could configure syslog-ng to set up a unix socket as a listener. Then whenever clients connect logs can be sent to the client. Syslog-ng currently has unix-stream and unix-dgram destinations, but they act as clients, only sending to already created sockets. There could be other uses for this, basically allowing clients to connect whenever they want and receive the logs. Kind of like a pipe destination, but it works a bit cleaner since if no client is connected, syslog-ng wouldnt have to buffer and drop messages (and it would allow multiple clients). Fairly low priority, but just something that I thought would be useful. -Patrick
Patrick Hemmer <syslogng@stormcloud9.net> writes:
Syslog-ng currently has unix-stream and unix-dgram destinations, but they act as clients, only sending to already created sockets. There could be other uses for this, basically allowing clients to connect whenever they want and receive the logs. Kind of like a pipe destination, but it works a bit cleaner since if no client is connected, syslog-ng wouldnt have to buffer and drop messages (and it would allow multiple clients).
Fairly low priority, but just something that I thought would be useful.
One of us is reading the other's mind. While working on another feature, I needed this, too, so I started exploring how to implement it best. It's far from done (I got sidetracked), but it's something reasonably high on my TODO list at the moment. I'll see if I can do something about it during my next syslog-ng sprint. -- |8]
participants (2)
-
Gergely Nagy
-
Patrick Hemmer