-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nixos/systemd: add upstreamSystemWants option #3106
nixos/systemd: add upstreamSystemWants option #3106
Conversation
👍 |
What exactly fails? I don't want to add options to work around bugs. |
It's not problem only the failure(well yeah mounting of few kernel On Fri, Jun 27, 2014 at 2:57 PM, Eelco Dolstra notifications@github.com
-----BEGIN PGP PUBLIC KEY BLOCK----- mQENBFEY1PEBCADPOfERF2wo4qeoq9L1m2z4pKfWqNd4B6BsoFUWPNd7BXmY+9JG |
But targets don't do anything except pull in other units. What units/services specifically don't you want? |
Ok i see, so specifically:
|
@edolstra So, are you OK with this customisation possibility? |
Ping |
@edolstra is there any drawback in merging this? Apparently is just adds a configuration option with the same default as before, so net win? |
Again, I don't see the point in an option to disable units that systemd won't even try to start anyway. If there actually are mount units that fail then they apparently lack a Condition to prevent them from being started, which should be fixed. |
@offlinehacker do you think that what @edolstra says is a better fix? |
You can close this issus. Docker was not ment for running whole os(well you
|
We need this for some lxc implementation like libcontainer docker, to disable uneeded targets, which fail at boot time.