How do I apply the changes from systemctl preset-all automatically without a reboot
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
systemctl preset-all changes which services are enabled or disabled. How can I (automatically) start and stop services to get the current machine into sync with the presets without manually starting and stopping services myself.
The aim is to get the machine into a state after running preset-all without a reboot that is the same as the state of the machine after a reboot.
e.g. if I enable service X in the presets and X wasn't previously running then I'd like it to start.
systemd
add a comment |Â
up vote
3
down vote
favorite
systemctl preset-all changes which services are enabled or disabled. How can I (automatically) start and stop services to get the current machine into sync with the presets without manually starting and stopping services myself.
The aim is to get the machine into a state after running preset-all without a reboot that is the same as the state of the machine after a reboot.
e.g. if I enable service X in the presets and X wasn't previously running then I'd like it to start.
systemd
In principle,systemctl isolate
your desired target graphical.target / multi-user.target or just default.target, which is symlinked to whichever you default to at boot time. In practice,isolate
is a bag of horrors, it manages to kill gui sessions somehow among other things. AFAIK there is no good way to do what you want. Don't use presets if this is what you want; it's why Debian hasn't converted to rely on them despite multiple references to Debian in the documentation for presets. Don't use isolate, or be prepared for it to blow up.
â sourcejedi
Mar 16 at 8:16
It's possiblesystemctl isolate multi-user
is somewhat less buggy. If you're using a gui, you might try that, and then follow up withsystemctl isolate graphical.target
. And then you know bad things will likely happen to your gui, so you'll be running it from a text console or remote login.
â sourcejedi
Mar 16 at 8:18
Righto.. that's very interesting. This is for a headless box but I don't like what I hear. Thanks for the hard-to-find info...
â demented hedgehog
Mar 17 at 0:48
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
systemctl preset-all changes which services are enabled or disabled. How can I (automatically) start and stop services to get the current machine into sync with the presets without manually starting and stopping services myself.
The aim is to get the machine into a state after running preset-all without a reboot that is the same as the state of the machine after a reboot.
e.g. if I enable service X in the presets and X wasn't previously running then I'd like it to start.
systemd
systemctl preset-all changes which services are enabled or disabled. How can I (automatically) start and stop services to get the current machine into sync with the presets without manually starting and stopping services myself.
The aim is to get the machine into a state after running preset-all without a reboot that is the same as the state of the machine after a reboot.
e.g. if I enable service X in the presets and X wasn't previously running then I'd like it to start.
systemd
edited Mar 16 at 1:09
asked Mar 16 at 0:28
demented hedgehog
1163
1163
In principle,systemctl isolate
your desired target graphical.target / multi-user.target or just default.target, which is symlinked to whichever you default to at boot time. In practice,isolate
is a bag of horrors, it manages to kill gui sessions somehow among other things. AFAIK there is no good way to do what you want. Don't use presets if this is what you want; it's why Debian hasn't converted to rely on them despite multiple references to Debian in the documentation for presets. Don't use isolate, or be prepared for it to blow up.
â sourcejedi
Mar 16 at 8:16
It's possiblesystemctl isolate multi-user
is somewhat less buggy. If you're using a gui, you might try that, and then follow up withsystemctl isolate graphical.target
. And then you know bad things will likely happen to your gui, so you'll be running it from a text console or remote login.
â sourcejedi
Mar 16 at 8:18
Righto.. that's very interesting. This is for a headless box but I don't like what I hear. Thanks for the hard-to-find info...
â demented hedgehog
Mar 17 at 0:48
add a comment |Â
In principle,systemctl isolate
your desired target graphical.target / multi-user.target or just default.target, which is symlinked to whichever you default to at boot time. In practice,isolate
is a bag of horrors, it manages to kill gui sessions somehow among other things. AFAIK there is no good way to do what you want. Don't use presets if this is what you want; it's why Debian hasn't converted to rely on them despite multiple references to Debian in the documentation for presets. Don't use isolate, or be prepared for it to blow up.
â sourcejedi
Mar 16 at 8:16
It's possiblesystemctl isolate multi-user
is somewhat less buggy. If you're using a gui, you might try that, and then follow up withsystemctl isolate graphical.target
. And then you know bad things will likely happen to your gui, so you'll be running it from a text console or remote login.
â sourcejedi
Mar 16 at 8:18
Righto.. that's very interesting. This is for a headless box but I don't like what I hear. Thanks for the hard-to-find info...
â demented hedgehog
Mar 17 at 0:48
In principle,
systemctl isolate
your desired target graphical.target / multi-user.target or just default.target, which is symlinked to whichever you default to at boot time. In practice, isolate
is a bag of horrors, it manages to kill gui sessions somehow among other things. AFAIK there is no good way to do what you want. Don't use presets if this is what you want; it's why Debian hasn't converted to rely on them despite multiple references to Debian in the documentation for presets. Don't use isolate, or be prepared for it to blow up.â sourcejedi
Mar 16 at 8:16
In principle,
systemctl isolate
your desired target graphical.target / multi-user.target or just default.target, which is symlinked to whichever you default to at boot time. In practice, isolate
is a bag of horrors, it manages to kill gui sessions somehow among other things. AFAIK there is no good way to do what you want. Don't use presets if this is what you want; it's why Debian hasn't converted to rely on them despite multiple references to Debian in the documentation for presets. Don't use isolate, or be prepared for it to blow up.â sourcejedi
Mar 16 at 8:16
It's possible
systemctl isolate multi-user
is somewhat less buggy. If you're using a gui, you might try that, and then follow up with systemctl isolate graphical.target
. And then you know bad things will likely happen to your gui, so you'll be running it from a text console or remote login.â sourcejedi
Mar 16 at 8:18
It's possible
systemctl isolate multi-user
is somewhat less buggy. If you're using a gui, you might try that, and then follow up with systemctl isolate graphical.target
. And then you know bad things will likely happen to your gui, so you'll be running it from a text console or remote login.â sourcejedi
Mar 16 at 8:18
Righto.. that's very interesting. This is for a headless box but I don't like what I hear. Thanks for the hard-to-find info...
â demented hedgehog
Mar 17 at 0:48
Righto.. that's very interesting. This is for a headless box but I don't like what I hear. Thanks for the hard-to-find info...
â demented hedgehog
Mar 17 at 0:48
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f430522%2fhow-do-i-apply-the-changes-from-systemctl-preset-all-automatically-without-a-reb%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
In principle,
systemctl isolate
your desired target graphical.target / multi-user.target or just default.target, which is symlinked to whichever you default to at boot time. In practice,isolate
is a bag of horrors, it manages to kill gui sessions somehow among other things. AFAIK there is no good way to do what you want. Don't use presets if this is what you want; it's why Debian hasn't converted to rely on them despite multiple references to Debian in the documentation for presets. Don't use isolate, or be prepared for it to blow up.â sourcejedi
Mar 16 at 8:16
It's possible
systemctl isolate multi-user
is somewhat less buggy. If you're using a gui, you might try that, and then follow up withsystemctl isolate graphical.target
. And then you know bad things will likely happen to your gui, so you'll be running it from a text console or remote login.â sourcejedi
Mar 16 at 8:18
Righto.. that's very interesting. This is for a headless box but I don't like what I hear. Thanks for the hard-to-find info...
â demented hedgehog
Mar 17 at 0:48