Knurpht - Gertjan Lettink writes:
You do not only need to start the new unit, bu also to enable it
Well, there was a reason I've thrown up my hands and asked for help… --8<---------------cut here---------------start------------->8--- # systemctl enable pps0.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 using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. --8<---------------cut here---------------end--------------->8--- So no, there must be something else; the udev rule has $ENV{SYSTEMD_WANTS}="pps0.service" as per a blog post I found so 3) should be applicable. I know that the udev rule has triggered, but not what, if anything, systemd did. How to debug this? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org