From: robin_listas@es.invalid   
      
   On 2025-12-29 04:39, Lawrence D’Oliveiro wrote:   
   > On Mon, 29 Dec 2025 03:15:14 +0100, Carlos E.R. wrote:   
   >   
   >> On 2025-12-29 03:08, Lawrence D’Oliveiro wrote:   
   >>>   
   >>> On Mon, 29 Dec 2025 00:16:48 -0000 (UTC), Lars Poulsen wrote:   
   >>>   
   >>>> On 2025-12-28, Lawrence D’Oliveiro  wrote:   
   >>>>>   
   >>>>> Or you could have looked further into the log with journalctl,   
   >>>>> and seen the appropriate message there.   
   >>>>   
   >>>> Not so simple. The journal from a system startup is about 4000   
   >>>> lines. Good luck finding something useful if you doni't know what   
   >>>> to search for.   
   >>>   
   >>>       journalctl -b _SYSTEMD_UNIT=«problem-service»   
   >>>   
   >>> to start with. I.e. look for error messages specifically relevant   
   >>> to the service that has trouble starting.   
   >>>   
   >>> Remember I’ve been there, done that.   
   >>   
   >> So did I.   
   >>   
   >> Telcontar:~ # journalctl -b 1 _SYSTEMD_UNIT=smb.service _SYST   
   MD_UNIT=nmb.service   
   >> -- No entries --   
   >> Telcontar:~ #   
   >   
   > Which boot instance is that “-b 1” supposed to correspond to?   
      
   The last one where the problem was happening and the one where I   
   bothered to investigate. The problem was solved on that boot, thanks to   
   ChatGPT who nailed it.   
      
   --   
   Cheers, Carlos.   
   ES🇪🇸, EU🇪🇺;   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)