From: Henrik.Carlqvist@deadspam.com   
      
   On Mon, 06 Mar 2023 13:47:15 -0500, Mike Small wrote:   
   > Do you remember any discussions describing this preference vs. other   
   > distros' for rsyslog or syslog-ng? Or do you have your own opinions?   
      
   I would say that it makes sense to use a syslog software derived from BSD   
   distributions as Slackware in other parts like starup scripts is rather   
   "BSD-like". However, my guess is that the main reason that sysklogd whas   
   choosen was the simple fact that neither syslog-ng (first release 1998)   
   or rsyslog (first release 2004) was available as choices back in the   
   early 90s when Slackware was initiated.   
      
   I once had the need to configure a log server where clients could send   
   their messages encrypted to the log server. As Slackware clients with   
   sysklogd does not natively support encryption to remote servers my   
   solution ended up using OpenVPN and connecting the sysklogd clients to an   
   IP address of the server in the OpenVPN network. I don't remember for   
   sure which software I used for the log server, but it was probably syslog-   
   ng or possibly rsyslog. However, that software was only used for the   
   collecting log server, the server which it ran to was also running   
   sysklogd.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)