Re: packages using non-standard ports
On 02/08/14 15:24, Ben Hutchings wrote:
> On Sat, 2014-08-02 at 13:05 +0200, Daniel Pocock wrote:
>> syslog-nagios-bridge needs to listen on a TCP port for connections from
>> rsyslogd or whatever
>> To make it easy for users (fully automated installation), I can
>> a) configure the package to listen on some port (I use 30514)
>> b) deploy a file /etc/rsyslog.d/nagios-bridge.conf with the config for
>> the same port
>> Doing this, the service starts working as soon as the package is installed.
>> Do people feel it is a good idea for packages to grab non-standard ports
>> like this?
> Not really, no. Isn't there a standard port for this? (Annoyingly
> 514/tcp is assigned to a completely different protocol.)
The syslog daemon itself usually listens on 514
It then relays a copy of every message to syslog-nagios-bridge on
localhost:30514 or whatever using the same Syslog protocol.
syslog-nagios-bridge shouldn't run on 514. Although it can receive
Syslog packets, it doesn't store them to file or database or any other
normal Syslog features.