home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.os.linux.misc      Linux-specific topics not covered by oth      135,536 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 134,938 of 135,536   
   Carlos E.R. to Marc Haber   
   Re: ever had 1GB+ kern.log (and syslog)    
   19 Jan 26 22:46:49   
   
   From: robin_listas@es.invalid   
      
   On 2026-01-19 15:53, Marc Haber wrote:   
   > "Carlos E.R."  wrote:   
   >> On 2026-01-19 09:56, Marc Haber wrote:   
   >>> "Carlos E.R."  wrote:   
   >>>> Syslog, before systemd intervened, managed to capture all messages just   
   >>>> fine.   
   >>>   
   >>> That was usually done by piping dmesg's output (the kernel ring   
   >>> buffer) to syslog later during system startup once syslog is running.   
   >>>   
   >>>> I am saying that systemd is not passing all the messages to syslog.   
   >>>   
   >>> It surely can be configured to do so. File a bug with your   
   >>> Distribution. The kernel ring buffer still exists.   
   >>   
   >> I will have to investigate one day what is going on.   
   >   
   > I bought a new notebook in late 2024 and deliberately didn't install   
   > syslog. Just to force myself to get more acquainted with journalctl   
   > since there will be a day when I'll have to fix a server that doesn't   
   > have syslog. THEN I won't have time to read up on journalctl.   
      
   Oh, I can use fine journalctl.   
   When I report on bugzilla I use that.   
      
   However, I do have problems with eliminating from the log the hugely verbose   
   news facility, mail facility, and authpriv. With the concoction I have, some   
   parts disappear, because they are not assigned any facility.   
      
      
    From one of my bugzillas:   
      
   journalctl --boot=-2 --facility=kern,user,daemon,auth,syslog,lpr   
   uucp,cron,authpriv,ftp,12,13,14,15,local0,local1,local2,local3,l   
   cal4,local5,local6,local7 > journal_purged   
      
      
   However, notice that several megabytes of messages like this:   
      
         Feb 18 12:17:58 Telcontar sddm[2599]: Initializing...   
      
   are also missing. They are facility 1, should not be removed. I know they are   
   fac 1 by comparison with syslog:   
      
       <1.4> 2025-02-24T01:03:30.963177+01:00 Telcontar sddm 2599 - -  Signal   
   received: SIGTERM   
        *..... I print the  numbers.   
      
   If you need those messages in the log, please advise how to remove mail and   
   news messages from the journal. Grep doesn't work because news messages are   
   multiline.   
      
      
      
   --   
   Cheers, Carlos.   
   ES🇪🇸, EU🇪🇺;   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca