Arch Linux User Repository

I have added init scripts for OpenRC, sysvinit, systemd.

Note that I am on an OpenRC system and not on a systemd-system. And I don't know much about systemd.

I made the systemd init file "blindly" and with some guesswork.

Please, submit in the comments how the systemd (and sysvinit) scripts can be made better or can be fixed in case they are broken.

Regards!

I now longer use an intel machine.

So I am disowning this.

Anyone wanting to maintain is warmly invited to adopt the package.

Regards!

I have added WantedBy=sysinit.target.

Thanks for the help.

I intentionally do not install in a way that after package installation it is automatically started, because I see it as bad practise when installation of a software (which can be used manually) forces a change in the startup process. The user should manually decide how to use the software and weather he/she wants automatic startup or not.

@dreieck:

can you say what a correct configuration might be, what a suitable target could be? I have no idea about systemd's targets.

I think sysinit.target is what we want. Just tried it and it works OK.
Also I realized WantedBy is not needed. We just need a symlink in "/usr/lib/systemd/system/sysinit.target.wants/" linking to the service file for it to be enabled from the install. Otherwise manual enabling is required.

@eduardoeae,

WantedBy= is commented out in phc-intel.service (Also I think multi-user.target is not the best target for this, but it gets the job done)

can you say what a correct configuration might be, what a suitable target could be? I have no idea about systemd's targets.

$ systemctl enable phc-intel.service
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.

WantedBy= is commented out in phc-intel.service (Also I think multi-user.target is not the best target for this, but it gets the job done)

@eduardoeae:

Thanks for reporting.

As I mentioned, I neither know about systemd nor an I test.

I now change the executable bit of the systemd service file.

But any deeper debugging must come from others.

Regards!

I get this from the journal in systemd:

Configuration file /usr/lib/systemd/system/phc-intel.service is marked executable. Please remove executable permission bits. Proceeding anyway.