From: ldo@nz.invalid   
      
   On Fri, 16 Jan 2026 22:23:08 +0100, Carlos E.R. wrote:   
      
   > I am using no scripting at all. I use the default toolset for   
   > handling syslog messages for decades of *nix.   
   >   
   > /etc/rsyslog.conf: (this configuration came with the system,   
   > commented out, so I just had to uncoment it)   
   >   
   > news.crit                               -/var/log/news/news.crit   
   > news.err                                -/var/log/news/news.err   
   > news.notice                             -/var/log/news/news.notice   
   > news.debug                              -/var/log/news/news.debug   
      
   This involves splitting out the messages into categories upfront, at   
   collection time, not analysis time.   
      
   > /etc/logrotate.d/syslog:    (this configuration is the same as default for   
   other files)   
   >   
   > [etc]   
      
   Same applies here.   
      
   > I want tools provided by the systemd people, not hacks.   
      
   Most data-collection philosophy is “collect everything first, split it   
   out for analysis later”. That seems to me more flexible than having to   
   decide up front how you want to divide up the raw data for analysis.   
   Because what happens if you change your mind about how you want to   
   analyze data you’ve already collected?   
      
   And it’s how the systemd tools work.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)