How to halt an attempted directory listing from pressing tab?
up vote
1
down vote
favorite
Sometimes I'll accidentally/instinctively double tab in a directory I probably shouldn't have. In the current case, the reason I'm writing this, it is on an old, very full cifs drive.
Of course, this causes the controlling terminal to hang waiting for the directory listing, Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
Is there any way to kill this listing? Is it something that's visible in a process list or do I just have to wait for the listing to come through (it doesn't seem like there's a timeout).
This is in Bash on Ubuntu 16.04.
Not a duplicate of "how to disable". I don't want to disable the feature, I want to know how to halt it when it's been run accidentally on a directory listing that will take a very long time.
linux autocomplete unresponsive
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
asked Dec 7 at 16:04
Brydon Gibson
358213
add a comment |
up vote
1
down vote
favorite
Sometimes I'll accidentally/instinctively double tab in a directory I probably shouldn't have. In the current case, the reason I'm writing this, it is on an old, very full cifs drive.
Of course, this causes the controlling terminal to hang waiting for the directory listing, Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
Is there any way to kill this listing? Is it something that's visible in a process list or do I just have to wait for the listing to come through (it doesn't seem like there's a timeout).
This is in Bash on Ubuntu 16.04.
Not a duplicate of "how to disable". I don't want to disable the feature, I want to know how to halt it when it's been run accidentally on a directory listing that will take a very long time.
linux autocomplete unresponsive
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
asked Dec 7 at 16:04
Brydon Gibson
358213
1
Possible duplicate of How to disable double tab to show available commands in Bash?
– harrymc
Dec 7 at 16:34
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Sometimes I'll accidentally/instinctively double tab in a directory I probably shouldn't have. In the current case, the reason I'm writing this, it is on an old, very full cifs drive.
Of course, this causes the controlling terminal to hang waiting for the directory listing, Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
Is there any way to kill this listing? Is it something that's visible in a process list or do I just have to wait for the listing to come through (it doesn't seem like there's a timeout).
This is in Bash on Ubuntu 16.04.
Not a duplicate of "how to disable". I don't want to disable the feature, I want to know how to halt it when it's been run accidentally on a directory listing that will take a very long time.
linux autocomplete unresponsive
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
asked Dec 7 at 16:04
Brydon Gibson
358213
Sometimes I'll accidentally/instinctively double tab in a directory I probably shouldn't have. In the current case, the reason I'm writing this, it is on an old, very full cifs drive.
Of course, this causes the controlling terminal to hang waiting for the directory listing, Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
Is there any way to kill this listing? Is it something that's visible in a process list or do I just have to wait for the listing to come through (it doesn't seem like there's a timeout).
This is in Bash on Ubuntu 16.04.
Not a duplicate of "how to disable". I don't want to disable the feature, I want to know how to halt it when it's been run accidentally on a directory listing that will take a very long time.
linux autocomplete unresponsive
linux autocomplete unresponsive
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
asked Dec 7 at 16:04
Brydon Gibson
358213
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
asked Dec 7 at 16:04
Brydon Gibson
358213
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
edited Dec 9 at 1:00
Kamil Maciorowski
23.5k155072
23.5k155072
asked Dec 7 at 16:04
Brydon Gibson
358213
asked Dec 7 at 16:04
Brydon Gibson
358213
asked Dec 7 at 16:04
Brydon Gibson
358213
358213
1
Possible duplicate of How to disable double tab to show available commands in Bash?
– harrymc
Dec 7 at 16:34
add a comment |
1
Possible duplicate of How to disable double tab to show available commands in Bash?
– harrymc
Dec 7 at 16:34
1
1
Possible duplicate of How to disable double tab to show available commands in Bash?
– harrymc
Dec 7 at 16:34
Possible duplicate of How to disable double tab to show available commands in Bash?
– harrymc
Dec 7 at 16:34
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
It's sending an interrupt to the right process but the process is in uninterruptible sleep.
An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.
In Unix-like systems the command
ps -luses codeDfor the uninterruptible sleep state of a process. Such processes cannot be killed even withSIGKILLand the only non-sophisticated way to get rid of them is to reboot the system.
So
Is there any way to kill this listing?
Reboot.
Is it something that's visible in a process list?
Yes. A process in D state.
do I just have to wait for the listing to come through?
Yes. Or reboot.
Related: What if kill -9 does not work?
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
add a comment |
Your Answer
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%2f1381683%2fhow-to-halt-an-attempted-directory-listing-from-pressing-tab%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
up vote
2
down vote
accepted
Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
It's sending an interrupt to the right process but the process is in uninterruptible sleep.
An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.
In Unix-like systems the command
ps -luses codeDfor the uninterruptible sleep state of a process. Such processes cannot be killed even withSIGKILLand the only non-sophisticated way to get rid of them is to reboot the system.
So
Is there any way to kill this listing?
Reboot.
Is it something that's visible in a process list?
Yes. A process in D state.
do I just have to wait for the listing to come through?
Yes. Or reboot.
Related: What if kill -9 does not work?
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
add a comment |
up vote
2
down vote
accepted
Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
It's sending an interrupt to the right process but the process is in uninterruptible sleep.
An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.
In Unix-like systems the command
ps -luses codeDfor the uninterruptible sleep state of a process. Such processes cannot be killed even withSIGKILLand the only non-sophisticated way to get rid of them is to reboot the system.
So
Is there any way to kill this listing?
Reboot.
Is it something that's visible in a process list?
Yes. A process in D state.
do I just have to wait for the listing to come through?
Yes. Or reboot.
Related: What if kill -9 does not work?
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
It's sending an interrupt to the right process but the process is in uninterruptible sleep.
An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.
In Unix-like systems the command
ps -luses codeDfor the uninterruptible sleep state of a process. Such processes cannot be killed even withSIGKILLand the only non-sophisticated way to get rid of them is to reboot the system.
So
Is there any way to kill this listing?
Reboot.
Is it something that's visible in a process list?
Yes. A process in D state.
do I just have to wait for the listing to come through?
Yes. Or reboot.
Related: What if kill -9 does not work?
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
Ctrl+C does nothing since it's sending an interrupt to the wrong process (the listing was spawned in a sub-shell, I assume).
It's sending an interrupt to the right process but the process is in uninterruptible sleep.
An uninterruptible sleep state is a sleep state that won't handle a signal right away. It will wake only as a result of a waited-upon resource becoming available or after a time-out occurs during that wait (if specified when put to sleep). It is mostly used by device drivers waiting for disk or network IO (input/output). When the process is sleeping uninterruptibly, signals accumulated during the sleep will be noticed when the process returns from the system call or trap.
In Unix-like systems the command
ps -luses codeDfor the uninterruptible sleep state of a process. Such processes cannot be killed even withSIGKILLand the only non-sophisticated way to get rid of them is to reboot the system.
So
Is there any way to kill this listing?
Reboot.
Is it something that's visible in a process list?
Yes. A process in D state.
do I just have to wait for the listing to come through?
Yes. Or reboot.
Related: What if kill -9 does not work?
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
edited Dec 9 at 6:22
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
answered Dec 9 at 0:55
Kamil Maciorowski
23.5k155072
23.5k155072
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1381683%2fhow-to-halt-an-attempted-directory-listing-from-pressing-tab%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
1
Possible duplicate of How to disable double tab to show available commands in Bash?
– harrymc
Dec 7 at 16:34