When opening Terminal: “NO LOGINS: System going down at 01:10”
I'm trying to get a terminal open, and I get this message:
NO LOGINS: System going down at 01:10
Login incorrect
login: *myname*
Login incorrect
login:
It doesn't prompt for my password. This happens with iTerm2 and Terminal.
I'm using zsh, and when I change my default command to bash it runs fine. Is it possible to get a zsh session open?
macos terminal zsh terminal.app
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
add a comment |
I'm trying to get a terminal open, and I get this message:
NO LOGINS: System going down at 01:10
Login incorrect
login: *myname*
Login incorrect
login:
It doesn't prompt for my password. This happens with iTerm2 and Terminal.
I'm using zsh, and when I change my default command to bash it runs fine. Is it possible to get a zsh session open?
macos terminal zsh terminal.app
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
Are you sure this is connected with your login shell? (How can you chage it when you can't login?) I would expect that if the systeme is scheduled for going down shortly that all logins except root are disabled.
– mpy
May 27 '14 at 16:26
@mpy in the iTerm (and I think terminal) prefs you can set the command that runs when a terminal is opened.
– JJJollyjim
May 27 '14 at 20:23
Try moving your ~/.zshrc file and seeing what happens.
– stib
Jun 4 '14 at 12:45
add a comment |
I'm trying to get a terminal open, and I get this message:
NO LOGINS: System going down at 01:10
Login incorrect
login: *myname*
Login incorrect
login:
It doesn't prompt for my password. This happens with iTerm2 and Terminal.
I'm using zsh, and when I change my default command to bash it runs fine. Is it possible to get a zsh session open?
macos terminal zsh terminal.app
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
I'm trying to get a terminal open, and I get this message:
NO LOGINS: System going down at 01:10
Login incorrect
login: *myname*
Login incorrect
login:
It doesn't prompt for my password. This happens with iTerm2 and Terminal.
I'm using zsh, and when I change my default command to bash it runs fine. Is it possible to get a zsh session open?
macos terminal zsh terminal.app
macos terminal zsh terminal.app
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
asked May 27 '14 at 7:37
JJJollyjimJJJollyjim
2871413
2871413
Are you sure this is connected with your login shell? (How can you chage it when you can't login?) I would expect that if the systeme is scheduled for going down shortly that all logins except root are disabled.
– mpy
May 27 '14 at 16:26
@mpy in the iTerm (and I think terminal) prefs you can set the command that runs when a terminal is opened.
– JJJollyjim
May 27 '14 at 20:23
Try moving your ~/.zshrc file and seeing what happens.
– stib
Jun 4 '14 at 12:45
add a comment |
Are you sure this is connected with your login shell? (How can you chage it when you can't login?) I would expect that if the systeme is scheduled for going down shortly that all logins except root are disabled.
– mpy
May 27 '14 at 16:26
@mpy in the iTerm (and I think terminal) prefs you can set the command that runs when a terminal is opened.
– JJJollyjim
May 27 '14 at 20:23
Try moving your ~/.zshrc file and seeing what happens.
– stib
Jun 4 '14 at 12:45
Are you sure this is connected with your login shell? (How can you chage it when you can't login?) I would expect that if the systeme is scheduled for going down shortly that all logins except root are disabled.
– mpy
May 27 '14 at 16:26
Are you sure this is connected with your login shell? (How can you chage it when you can't login?) I would expect that if the systeme is scheduled for going down shortly that all logins except root are disabled.
– mpy
May 27 '14 at 16:26
@mpy in the iTerm (and I think terminal) prefs you can set the command that runs when a terminal is opened.
– JJJollyjim
May 27 '14 at 20:23
@mpy in the iTerm (and I think terminal) prefs you can set the command that runs when a terminal is opened.
– JJJollyjim
May 27 '14 at 20:23
Try moving your ~/.zshrc file and seeing what happens.
– stib
Jun 4 '14 at 12:45
Try moving your ~/.zshrc file and seeing what happens.
– stib
Jun 4 '14 at 12:45
add a comment |
1 Answer
1
active
oldest
votes
I don't know why, but I resolved it by deleting the file nologin inside the /etc/ folder.
Perhaps here is some explanation, from the book A Practical Guide to UNIX for Mac OS X Users, by Mark G. Sobell and Peter Seebach:
The pam_nologin module makes sure that if the /etc/nologin file exists, only the root user is allowed to log in. (That is, the pam_nologin module reports success only if /etc/nologin does not exist or if the root user is logging in.) Thus, when a shutdown has been scheduled in the near future, the system administrator can keep users from logging in on the system only to experience a shutdown moments later.
edited Sep 9 '15 at 9:59
Arjan
27k1065107
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f759164%2fwhen-opening-terminal-no-logins-system-going-down-at-0110%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
I don't know why, but I resolved it by deleting the file nologin inside the /etc/ folder.
Perhaps here is some explanation, from the book A Practical Guide to UNIX for Mac OS X Users, by Mark G. Sobell and Peter Seebach:
The pam_nologin module makes sure that if the /etc/nologin file exists, only the root user is allowed to log in. (That is, the pam_nologin module reports success only if /etc/nologin does not exist or if the root user is logging in.) Thus, when a shutdown has been scheduled in the near future, the system administrator can keep users from logging in on the system only to experience a shutdown moments later.
edited Sep 9 '15 at 9:59
Arjan
27k1065107
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
add a comment |
I don't know why, but I resolved it by deleting the file nologin inside the /etc/ folder.
Perhaps here is some explanation, from the book A Practical Guide to UNIX for Mac OS X Users, by Mark G. Sobell and Peter Seebach:
The pam_nologin module makes sure that if the /etc/nologin file exists, only the root user is allowed to log in. (That is, the pam_nologin module reports success only if /etc/nologin does not exist or if the root user is logging in.) Thus, when a shutdown has been scheduled in the near future, the system administrator can keep users from logging in on the system only to experience a shutdown moments later.
edited Sep 9 '15 at 9:59
Arjan
27k1065107
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
add a comment |
I don't know why, but I resolved it by deleting the file nologin inside the /etc/ folder.
Perhaps here is some explanation, from the book A Practical Guide to UNIX for Mac OS X Users, by Mark G. Sobell and Peter Seebach:
The pam_nologin module makes sure that if the /etc/nologin file exists, only the root user is allowed to log in. (That is, the pam_nologin module reports success only if /etc/nologin does not exist or if the root user is logging in.) Thus, when a shutdown has been scheduled in the near future, the system administrator can keep users from logging in on the system only to experience a shutdown moments later.
edited Sep 9 '15 at 9:59
Arjan
27k1065107
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
I don't know why, but I resolved it by deleting the file nologin inside the /etc/ folder.
Perhaps here is some explanation, from the book A Practical Guide to UNIX for Mac OS X Users, by Mark G. Sobell and Peter Seebach:
The pam_nologin module makes sure that if the /etc/nologin file exists, only the root user is allowed to log in. (That is, the pam_nologin module reports success only if /etc/nologin does not exist or if the root user is logging in.) Thus, when a shutdown has been scheduled in the near future, the system administrator can keep users from logging in on the system only to experience a shutdown moments later.
edited Sep 9 '15 at 9:59
Arjan
27k1065107
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
edited Sep 9 '15 at 9:59
Arjan
27k1065107
edited Sep 9 '15 at 9:59
Arjan
27k1065107
edited Sep 9 '15 at 9:59
Arjan
27k1065107
27k1065107
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
answered Sep 9 '15 at 7:52
MaurizioMaurizio
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f759164%2fwhen-opening-terminal-no-logins-system-going-down-at-0110%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
Are you sure this is connected with your login shell? (How can you chage it when you can't login?) I would expect that if the systeme is scheduled for going down shortly that all logins except root are disabled.
– mpy
May 27 '14 at 16:26
@mpy in the iTerm (and I think terminal) prefs you can set the command that runs when a terminal is opened.
– JJJollyjim
May 27 '14 at 20:23
Try moving your ~/.zshrc file and seeing what happens.
– stib
Jun 4 '14 at 12:45