You are not logged in.
In my ever ongoing quest to understand systemd booting and noting, that alsa-restore is a static service, I am wondering, how can I find out, what other unit made this service start?
# cd /usr/lib/systemd/system
# grep -ir 'alsa-restore' *.target
# grep -ir 'alsa-restore' *.service
#
Nothing here, that would pull in alsa-restore. So, what does actually start it? Or rather, more in general, how can I find out, what loaded static service has been started by what other unit as a dependency? Kind of looking for a reverse dependency tree for service foo.
Last edited by EdeWolf (2016-05-18 21:02:54)
Offline
Not a Sysadmin issue, moving to NC...
Offline
In my ever ongoing quest to understand systemd booting and noting, that alsa-restore is a static service, I am wondering, how can I find out, what other unit made this service start?
# cd /usr/lib/systemd/system # grep -ir 'alsa-restore' *.target # grep -ir 'alsa-restore' *.service #
Nothing here, that would pull in alsa-restore. So, what does actually start it? Or rather, more in general, how can I find out, what loaded static service has been started by what other unit as a dependency? Kind of looking for a reverse dependency tree for service foo.
You mean like 'systemctl list-dependencies --reverse'?
man systemctl
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thanks for answering, thats it!
Offline