[systemd-devel] systemctl isolate "foo.service" expands to "foo.service.target"

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Fri Nov 28 08:30:15 PST 2014


On Fri, Nov 28, 2014 at 10:40:31AM -0500, Chris Atkinson wrote:
> I created a named snapshot:
> 
> $ sudo systemctl snapshot derpy
> derpy.snapshot
> 
> I tried restoring the named snapshot, but the mandatory mangling
> to .target got in the way:
> 
> $ sudo systemctl isolate derpy.snapshot
> Failed to start derpy.snapshot.target: Operation refused, unit may not
> be isolated.

This was an unintended side effect. I will push a commit to only
append the suffix in there isn't one already. If I say 'systemctl
set-default goo.device' I want to get an error, not get promoted to
goo.device.service.

Zbyszek


More information about the systemd-devel mailing list