Harry Putnam <[email protected]> writes:

> Thanks for your patience Rainer... ok I get it now.  But see comment
> at the end.

After saying that about something at the end.... I forgot to include
it.

I was just wondering why the example config that comes with the
rsyslog distro leaves out such important stuff as what it takes to get
the server listening for log messages.

It has a commented section that claims to be about:
 `Receiving Messages from Remote Hosts'

  # ######### Receiving Messages from Remote Hosts ########## 
  # TCP Syslog Server:
  # provides TCP syslog reception and GSS-API (if compiled to support it)
  #$ModLoad imtcp.so  # load module
  # Note: as of now, you need to use the -t command line option to
  # enable TCP reception (e.g. -t514 to run a server at port 514/tcp)
  # This will change in later v3 releases.
  
  # UDP Syslog Server:
  #$ModLoad imudp.so  # provides UDP syslog reception
  #$UDPServerRun 514 # start a UDP syslog server at standard port 514

But it doesn't bother to include the things that make tcp work, like
the all important lines posted by Aaron N.

  $InputTCPMaxSessions 1000 # Maximum TCP sessions (default 200)
  $InputTCPServerRun 514 # start up TCP listener at port 514

Again thank you both for your input and for website too Rainer.

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to