Howdy. I've got a "Resize file system" service that wants
first-boot-complete.target and is to be run before it. I've linked the service
to the first-boot-complete.target, removed /etc/machine-id and then reboot. The
first boot condition is met, yet I see the following status once booted:
○ res
> On 8 Apr 2025, at 2:40 PM, Andrei Borzenkov wrote:
>
> It cannot be the complete file because earlier it says "enabled" and this
> service does not have [Install] section.
>
> Anyway - something has to start this service. So far, you did not explain how
> it is started.
It is the complete
> On 9 Apr 2025, at 19:52, Windl, Ulrich wrote:
>
> Wasn't there an agreement that "wanting a target" is always wrong? Isn't
> "After" you are after? 😉
I’m unsure. I modelled my service on the first boot service.
Here are my sample unit files extracted from my real ones. Firstly, here is an
example of Service A:
[Unit]
Description=Service A
After=network.target
[Service]
Type=notify
NotifyAccess=all
...
[Install]
WantedBy=multi-user
> On 23 Jun 2025, at 4:12 PM, Andrei Borzenkov wrote:
>
> How A.service and B.service are started exactly?
systemctl enable A
systemctl enable B
reboot
Howdy,
I’m looking for some clarification on BindsTo as I’m wondering if there’s some
clarification required in the doc (1). I think I’m perhaps misinterpreting what
the doc is referring to as “active" i.e:
"When used in conjunction with After= on the same unit the behaviour of
BindsTo= is eve
