From: BitTwister@mouse-potato.com   
      
   On Sun, 8 Aug 2021 09:39:39 -0800, Sidney_Kotic wrote:   
   >   
   > Aug 08 08:28:44 crab SuSEfirewall2[1365]: Firewall rules successfully set   
   > Aug 08 08:28:44 crab systemd[1]: Finished SuSEfirewall2 phase 2.   
   >   
   > Not much to see there.  Nothing that tells me why it wasn't started.  Where,   
   in   
   > the filesystem, would I look to see how systemd should do that?   
      
   Systemd Unit files control unit operation. Unless configured otherwise   
   information is written into the journal file and can be viewed via journalctl.   
   As root run,    systemctl list-units --type=service | grep fail   
      
   Adding the systemd-journal group to your login id, log out/in will allow you   
   to view   
   the system journal information without having to be root.   
      
   man journalctl for journalctl usage.   
      
   if looking for firewall messages I would try   
     journalctl | grep -i firewall   
      
   Want to see how systemd usees unit files:   
    systemd-analyze plot > /var/tmp/blame.svg   
    firefox  /var/tmp/blame.svg &   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)