Systemd user service not starting at boot even though lingering is enabled (user via NIS)
Clash Royale CLAN TAG#URR8PPP
Lingering has been enabled with
loginctl enable-linger
However, the user services do not start before logging in with the user. The services remain active when logging out again.
Is something extra needed to make it work when the user is not in the /etc/passwd file, but provided via NIS ?
The service is correctly added to the default.target, so this seems to be unrelated to Why doesn't my systemd user unit start at boot?
systemd logind
asked Jan 28 at 10:03
RubenRuben
1365
add a comment |
Lingering has been enabled with
loginctl enable-linger
However, the user services do not start before logging in with the user. The services remain active when logging out again.
Is something extra needed to make it work when the user is not in the /etc/passwd file, but provided via NIS ?
The service is correctly added to the default.target, so this seems to be unrelated to Why doesn't my systemd user unit start at boot?
systemd logind
asked Jan 28 at 10:03
RubenRuben
1365
add a comment |
Lingering has been enabled with
loginctl enable-linger
However, the user services do not start before logging in with the user. The services remain active when logging out again.
Is something extra needed to make it work when the user is not in the /etc/passwd file, but provided via NIS ?
The service is correctly added to the default.target, so this seems to be unrelated to Why doesn't my systemd user unit start at boot?
systemd logind
asked Jan 28 at 10:03
RubenRuben
1365
Lingering has been enabled with
loginctl enable-linger
However, the user services do not start before logging in with the user. The services remain active when logging out again.
Is something extra needed to make it work when the user is not in the /etc/passwd file, but provided via NIS ?
The service is correctly added to the default.target, so this seems to be unrelated to Why doesn't my systemd user unit start at boot?
systemd logind
systemd logind
asked Jan 28 at 10:03
RubenRuben
1365
asked Jan 28 at 10:03
RubenRuben
1365
asked Jan 28 at 10:03
RubenRuben
1365
asked Jan 28 at 10:03
RubenRuben
1365
asked Jan 28 at 10:03
RubenRuben
1365
1365
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Interesting. network-online.target is not pulled in by default, so I don't think systemd-logind does anything with it; I guess logind doesn't know it needs to wait for your user details to become available...
Look up nss-user-lookup.target. Maybe you're supposed to create a drop-in file so that nss-user-lookup.target gains Wants= and After= on network-online.target.
The comment in nss-user-lookup.target does not sound like your needs were anticipated. "This exists mostly for implementations lacking socket/bus activation."
I believe SSSD implements caching for offline access. So maybe when you use SSSD it could just work, without having to make everything wait for wifi.
It looks like non-SSSD solutions can also provide caching for offline access, but the default setting might not cache for long enough: https://wiki.debian.org/LDAP/NSS#Offline_caching_of_NSS_with_nscd
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497165%2fsystemd-user-service-not-starting-at-boot-even-though-lingering-is-enabled-user%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Interesting. network-online.target is not pulled in by default, so I don't think systemd-logind does anything with it; I guess logind doesn't know it needs to wait for your user details to become available...
Look up nss-user-lookup.target. Maybe you're supposed to create a drop-in file so that nss-user-lookup.target gains Wants= and After= on network-online.target.
The comment in nss-user-lookup.target does not sound like your needs were anticipated. "This exists mostly for implementations lacking socket/bus activation."
I believe SSSD implements caching for offline access. So maybe when you use SSSD it could just work, without having to make everything wait for wifi.
It looks like non-SSSD solutions can also provide caching for offline access, but the default setting might not cache for long enough: https://wiki.debian.org/LDAP/NSS#Offline_caching_of_NSS_with_nscd
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
add a comment |
Interesting. network-online.target is not pulled in by default, so I don't think systemd-logind does anything with it; I guess logind doesn't know it needs to wait for your user details to become available...
Look up nss-user-lookup.target. Maybe you're supposed to create a drop-in file so that nss-user-lookup.target gains Wants= and After= on network-online.target.
The comment in nss-user-lookup.target does not sound like your needs were anticipated. "This exists mostly for implementations lacking socket/bus activation."
I believe SSSD implements caching for offline access. So maybe when you use SSSD it could just work, without having to make everything wait for wifi.
It looks like non-SSSD solutions can also provide caching for offline access, but the default setting might not cache for long enough: https://wiki.debian.org/LDAP/NSS#Offline_caching_of_NSS_with_nscd
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
add a comment |
Interesting. network-online.target is not pulled in by default, so I don't think systemd-logind does anything with it; I guess logind doesn't know it needs to wait for your user details to become available...
Look up nss-user-lookup.target. Maybe you're supposed to create a drop-in file so that nss-user-lookup.target gains Wants= and After= on network-online.target.
The comment in nss-user-lookup.target does not sound like your needs were anticipated. "This exists mostly for implementations lacking socket/bus activation."
I believe SSSD implements caching for offline access. So maybe when you use SSSD it could just work, without having to make everything wait for wifi.
It looks like non-SSSD solutions can also provide caching for offline access, but the default setting might not cache for long enough: https://wiki.debian.org/LDAP/NSS#Offline_caching_of_NSS_with_nscd
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
Interesting. network-online.target is not pulled in by default, so I don't think systemd-logind does anything with it; I guess logind doesn't know it needs to wait for your user details to become available...
Look up nss-user-lookup.target. Maybe you're supposed to create a drop-in file so that nss-user-lookup.target gains Wants= and After= on network-online.target.
The comment in nss-user-lookup.target does not sound like your needs were anticipated. "This exists mostly for implementations lacking socket/bus activation."
I believe SSSD implements caching for offline access. So maybe when you use SSSD it could just work, without having to make everything wait for wifi.
It looks like non-SSSD solutions can also provide caching for offline access, but the default setting might not cache for long enough: https://wiki.debian.org/LDAP/NSS#Offline_caching_of_NSS_with_nscd
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
answered Jan 28 at 13:03
sourcejedisourcejedi
24.3k440107
24.3k440107
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497165%2fsystemd-user-service-not-starting-at-boot-even-though-lingering-is-enabled-user%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
