Score:0

Systemd does not obey After= in Unit section

tn flag

I have a simple service that needs to start after the bluetooth.service unit and a couple others:

[Unit]
Description=My Application
Requires=bluetooth.service some.service another.service
After=bluetooth.service some.service another.service

[Service]
Type=dbus
BusName=my.bus.name1
ExecStart=/path/to/my/app
StandardOutput=journal
StandardError=journal

This seems pretty standard. Yet this service still always starts before bluetooth.service: analysis

Additionally, I can see that the services are correctly listed here:

# systemctl list-dependencies --after myapp.service
myapp.service
● ├─some.service
● ├─another.service
● ├─bluetooth.service
... etc.

My service is not an explicit dependency of anything else. Can anyone help me understand why this would happen?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.