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

2014-11-28 Thread Chris Atkinson
How does this interact with snapshots? While I was looking at man systemctl it seems that one uses isolate to restore to a previous snapshot: Snapshot Commands snapshot [NAME] Create a snapshot. If a snapshot name is specified, the new snapshot will be named after it. If

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

2014-11-28 Thread Zbigniew Jędrzejewski-Szmek
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

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

2014-11-28 Thread Chris Atkinson
The commit (5e03c6e3b517286bbd65b48d88f60e5b83721894) seems to be having some side effects. When I attempt to query status, stop or start a service I get the following: $ sudo systemctl stop transmission Assertion 'suffix' failed at src/shared/unit-name.c:515, function

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

2014-11-28 Thread Zbigniew Jędrzejewski-Szmek
On Fri, Nov 28, 2014 at 01:09:18PM -0500, Chris Atkinson wrote: The commit (5e03c6e3b517286bbd65b48d88f60e5b83721894) seems to be having some side effects. When I attempt to query status, stop or start a service I get the following: $ sudo systemctl stop transmission Assertion 'suffix'

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

2014-11-28 Thread Chris Atkinson
Commit e80733be33e52d8ab2f1ae845326d39c600f5612 seems to have done the trick. I'm able to start, stop and status services, isolate .target and .snapshot files and a filename with no extension following isolate is treated as a .target, all of which seems right. The systemctl man page will still

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

2014-11-28 Thread Zbigniew Jędrzejewski-Szmek
On Fri, Nov 28, 2014 at 02:02:24PM -0500, Chris Atkinson wrote: Commit e80733be33e52d8ab2f1ae845326d39c600f5612 seems to have done the trick. I'm able to start, stop and status services, isolate .target and .snapshot files and a filename with no extension following isolate is treated as a

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

2014-11-27 Thread WANG Chao
Hi, All I happen to notice systemctl isolate will expands foo.service to foo.service.target, which unfortunately breaks my boot in some way. I find the following commit: commit 0807312 Author: Lennart Poettering lenn...@poettering.net Date: Mon Oct 13 15:43:09 2014 +0200 systemctl: when

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

2014-11-27 Thread Andrei Borzenkov
В Fri, 28 Nov 2014 15:11:29 +0800 WANG Chao chaow...@redhat.com пишет: Hi, All I happen to notice systemctl isolate will expands foo.service to foo.service.target, which unfortunately breaks my boot in some way. I find the following commit: commit 0807312 Author: Lennart Poettering

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

2014-11-27 Thread WANG Chao
On 11/28/14 at 10:13am, Andrei Borzenkov wrote: В Fri, 28 Nov 2014 15:11:29 +0800 WANG Chao chaow...@redhat.com пишет: Hi, All I happen to notice systemctl isolate will expands foo.service to foo.service.target, which unfortunately breaks my boot in some way. I find the following