On Tue, 03.02.15 21:03, Brandon Philips (bran...@ifup.co) wrote:
Hey Lennart-
On Tue, Feb 3, 2015 at 10:32 AM, Brandon Philips bran...@ifup.co wrote:
On Tue, Feb 3, 2015 at 10:20 AM, Lennart Poettering
lenn...@poettering.net wrote:
I have added DefaultDependencies= for you now:
Hey Lennart-
On Tue, Feb 3, 2015 at 10:32 AM, Brandon Philips bran...@ifup.co wrote:
On Tue, Feb 3, 2015 at 10:20 AM, Lennart Poettering
lenn...@poettering.net wrote:
I have added DefaultDependencies= for you now:
On Mon, 15.12.14 17:44, Brandon Philips (bran...@ifup.co) wrote:
Hello-
How is a user supposed to disable DefaultDependencies on a scope? From
the docs it seems like it should work:
Unless DefaultDependencies=false is used, scope units will implicitly
have dependencies of type Conflicts=
On Tue, Feb 3, 2015 at 10:20 AM, Lennart Poettering
lenn...@poettering.net wrote:
I have added DefaultDependencies= for you now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=261420ba2a20305ad271b6f5f380aa74c5c9dd50
Thank you. I will work on getting Docker fixed up to fix this
Hello-
How is a user supposed to disable DefaultDependencies on a scope? From
the docs it seems like it should work:
Unless DefaultDependencies=false is used, scope units will implicitly
have dependencies of type Conflicts= and Before= on shutdown.target.
But, in practice:
systemd-run --scope
