[systemd-devel] Antw: [EXT] Re: Q: Debugging missing requirements

[Dave Howorth]

On Fri, 12 Feb 2021 18:04:58 +0300
Andrei Borzenkov <arvidjaar at gmail.com> wrote:
> 12.02.2021 10:04, Ulrich Windl пишет:
> >>>> Andrei Borzenkov <arvidjaar at gmail.com> schrieb am 11.02.2021 um
> >>>> 15:20 in  
> > Nachricht
> > <CAA91j0VND=nJSDpK30_=fTxd5DoChqRLd=XJOLzKnqoLV1Jjkg at mail.gmail.com>:  
> >> On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl
> >> <Ulrich.Windl at rz.uni-regensburg.de> wrote:  
> >>>
> >>> Hi!
> >>>
> >>> Suspecting systemd added some requirement that isn't fulfilled
> >>> after boot,   
> >> preventing my units from starting I wonder:  
> >>> How can I debug systemd's requirements checking for units that
> >>> are enabled,   
> >> but not started at boot (status "inactive (dead)"?
> >>
> >> Usual advice is - enable debug logging.  
> > 
> > Can I enable this for a specific unit, or just globally?
> 
> Not that I am aware of. It is all or nothing.

But you don't need to look at them all for other units. You can use
--priority to view just the levels you wish to. So there'll be more
information in the log files, but no need to look at it unless you wish
to.

> >>  
> >>> Or another way: Can I list the dependencies that systemd added   
> >> automatically?  
> >>>  
> >>
> >> If you mean implicit or default dependencies - no. They are listed
> >> in man pages, although there is no guarantee that list is
> >> complete. Your best bet is source code.  
> > 
> > 
> > 
> >   
> 
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel