First of all, the Mount unit type should implement the UnitInterface similar to the Timer or Service.
Despite that everything, that is possible with a Timer should also be possible with a Mount.

In the most simple case, you only need to provide the Mount class implenting the UnitInterface extending AbstractUnit. The class should provide the correct suffix.

For more information about a Unit or Mount see systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
https://www.freedesktop.org/software/systemd/man/systemd.mount.html

Also see PR #27 from @peter279k for reference.

First of all, the Device unit type should implement the UnitInterface similar to the Timer or Service.
Despite that everything, that is possible with a Timer should also be possible with a Device.

In the most simple case, you only need to provide the Device class implenting the UnitInterface extending AbstractUnit. The class should provide the correct suffix.

For more information about a Unit or Device see systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
https://www.freedesktop.org/software/systemd/man/systemd.device.html

Also see PR #27 from @peter279k for reference.

If there are units in failed state we can't clear the list of units using disable() or stop().
These units needs to be removed using systemctl reset-failed.

We need to introduce a new method similar to daemonReload()

When running the vendor/bin/phpunit with php-7.4 and PHPUnit 9.4.x versions, it presents following message:

PHPUnit 9.4.2 by Sebastian Bergmann and contributors.

Warning:       Your XML configuration validates against a deprecated schema.
Suggestion:    Migrate your XML configuration using "--migrate-configuration"!

And I think we can consider using the vendor/bin/phpunit --migrate-configuration to resolve this issue.

First of all, the Swap unit type should implement the UnitInterface similar to the Timer or Service.
Despite that everything, that is possible with a Timer should also be possible with a Swap.

In the most simple case, you only need to provide the Swap class implementing the UnitInterface extending AbstractUnit. The class should provide the correct suffix.

For more information about a Unit or Swap see systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
https://www.freedesktop.org/software/systemd/man/systemd.swap.html

Also see PR #27 from @peter279k for reference.

Currently the ProcessBuilder is a hard wired dependency of SystemCtl.
Adding this as an optional dependency will improve testability for mocking the ProcessBuilder.

Something like
$systemCtl->setProcessBuilderBuilder($processBuilder)

There should not be an required dependency in the constructor. This way the default construction is still valid. The getProcessBuilder() should be used to call the ProcessBuilderBuilder for an instance of ProcessBuilder

This should be done for v0.x as well as v1.x

First of all, the Slice unit type should implement the UnitInterface similar to the Timer or Service.
Despite that everything, that is possible with a Timer should also be possible with a Slice.

In the most simple case, you only need to provide the Slice class implementing the UnitInterface extending AbstractUnit. The class should provide the correct suffix.

For more information about a Unit or Slice see systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
https://www.freedesktop.org/software/systemd/man/systemd.slice.html

Also see PR #27 from @peter279k for reference.

First of all, the Target unit type should implement the UnitInterface similar to the Timer or Service.
Despite that everything, that is possible with a Timer should also be possible with a Target.

In the most simple case, you only need to provide the Target class implementing the UnitInterface extending AbstractUnit. The class should provide the correct suffix.

For more information about a Unit or Target see systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
https://www.freedesktop.org/software/systemd/man/systemd.target.html

Also see PR #27 from @peter279k for reference.

I'm no expert on systemctl or its related technology, far from it.
I do know that systemctl and systemctl --user are two separated concepts on the linux distro I'm working with.

At first glance it doesn't seem possible to add the option user to the command.

Running ->getService('test') works if the unit test is configured as a system unit.

$ systemctl status test

Running ->getService('test') works if the unit test is configured as a user unit but throws an (expected) UnitNotFoundException exception.

$ systemctl --user status test

I hope this is on the road map or, better yet, I'm just missing the obvious solution.

Calling is-active on a non active unit will return a non zero exit code. This will throw a CommandFailedException which is not entirely true.

If you need sudo, you should execute the bin executable with sudo. The incode support was dropped due to security reason.

How can I do this? If I do this:
$cmd = "php_systemctl"; \SystemCtl\SystemCtl::setBinary("sudo $cmd");
I get an error:
sh: sudo /home/.../php_systemctl: No such file or directory

Currently the UnitInstaller does not work with user scope.
The $installPath is fix for system scope installations.

This should work similar to switching the scope to find a unit.

$systemCtl->user()->install($template); // default: ~/.config/systemd/user/
$systemCtl->system()->install($template); // default: /etc/systemd/system/

user home should be retrieved automatically.
http://php.net/manual/en/function.posix-getpwuid.php

To resolve the paths we should use the currently empty PathResolver

https://github.com/symfony/process/blob/master/CHANGELOG.md#400

The changelog does not look like something that would concern this library. Could you make the constraint allow either ^3.0 or ^4.0, please?

First of all, the Automount unit type should implement the UnitInterface similar to the Timer or Service.
Despite that everything, that is possible with a Timer should also be possible with a Automount.

In the most simple case, you only need to provide the Automount class implenting the UnitInterface extending AbstractUnit. The class should provide the correct suffix.

For more information about a Unit or Automount see systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
https://www.freedesktop.org/software/systemd/man/systemd.automount.html

Also see PR #27 from @peter279k for reference.

Are there any plans to add the ability to create services?
man page: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Managing_Services_with_systemd-Unit_Files.html

Symfony ProcessBuilder is marked as deprecated - update symfony/process to ^4.0

Hi.

Would it be possible to add a status command, so we can check if a service is currently running, or is enabled?

Thanks