Systemd – How to Enable Systemd Service with a Parameter

servicesystemd

I have a systemd service with a paramter. It's working great. However, I cannot start it without a parameter.

The parameter would look like systemctl start [email protected], where the 1-0 would be parsed by a php script. The php script has a default of 1-0, but I cannot start it with systemctl start [email protected]. It tells me:

Failed to start [email protected]: Unit name [email protected] is missing the instance name.

I successfully enabled it with systemctl enable [email protected], but is it going to fail on boot? If so, how can I tell it to start with a default of 1-0 if nothing else is specified?

Best Answer

It appears that enabling a service with a default parameter is possible, per this guide. Since it needs to default to 1-0, I just did:

systemctl enable my-service\@1-0.service

It successfully created the symlink:

Created symlink /etc/systemd/system/multi-user.target.wants/[email protected] → /lib/systemd/system/[email protected]

Thanks for the downvote btw. Stay classy.

"Fine... I'll do it myself." ~ Thanos

Related Solutions

Systemd – How to Set Environment Variable in Service

Times change and so do best practices.

The current best way to do this is to run systemctl edit myservice, which will create an override file for you or let you edit an existing one.

In normal installations this will create a directory /etc/systemd/system/myservice.service.d, and inside that directory create a file whose name ends in .conf (typically, override.conf), and in this file you can add to or override any part of the unit shipped by the distribution.

For instance, in a file /etc/systemd/system/myservice.service.d/myenv.conf:

[Service]
Environment="SECRET=pGNqduRFkB4K9C2vijOmUDa2kPtUhArN"
Environment="ANOTHER_SECRET=JP8YLOc2bsNlrGuD6LVTq7L36obpjzxd"

Also note that if the directory exists and is empty, your service will be disabled! If you don't intend to put something in the directory, ensure that it does not exist.

For reference, the old way was:

The recommended way to do this is to create a file /etc/sysconfig/myservice which contains your variables, and then load them with EnvironmentFile.

For complete details, see Fedora's documentation on how to write a systemd script.

Docker – Reset / Ingnore non-zero exit code with fleet / systemd

You could prefix your command with -, then systemd ignores the failure and won't put the unit into a failed state. So, instead of

ExecStart=/path/to/your/command

Try

ExecStart=-/path/to/your/command

See systemd man page for more.

Best Answer

Related Solutions

Systemd – How to Set Environment Variable in Service

Docker – Reset / Ingnore non-zero exit code with fleet / systemd

Related Topic