Mdthbs

Do I need to be legally qualified to install a Hive smart thermostat?

How to create a 2D table with varying step?

Misaligned Columns

Language Selector

Construction of the word подтвержда́ть

Is it possible to spoof an IP address to an exact number?

Bypass with wrong cvv of debit card and getting OTP

Has there ever been a cold war other than between the U.S. and the U.S.S.R.?

Who are the police in Hong Kong?

Go function to test whether a file exists

Can Monks cast spells?

What is the difference between a historical drama and a period drama?

What does the ash content of broken wheat really mean?

CPLEX exceeds time limit issue

List of Implementations for common OR problems

What is the right way to query an I2C device from an interrupt service routine?

Hiding a solar system in a nebula

how to set the columns in pandas

What is -(-2,3,4)?

What is the difference between figures illustration and images?

What is the meaning of "stock" dilution on the Massive Dev Chart website?

Contributing to a candidate as a Foreign National US Resident?

gzip compress a local folder and extract it to remote server

Pandas merge and fillna

Why gnome-terminal tells me “There is still a process running” while logged in as root?

How can I launch gnome-terminal with unique titles for multiple tabs?Why does F10 in gnome-terminal open the right-click menu?Why some gnome-terminal tabs look depressedgnome-terminal: cursor blinks in inactive windowHow can I get the root terminal to add myself into sudoers file so that I can act as root?Gnome-terminal cannot send EOF after pasting huge amount of dataGnome Terminal not openingTerminal doesn't open after doing “screenfetch”Why can I open the Root Terminal only once? [Debian 9]Script continues execution after call to gnome-terminal

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

1

1

I'm using gnome on Debian Jessie. When I tried to close terminal after logged in as root, it told me like in the picture below.

What should I do to prevent this from happening again? Is it a bug??

Thanks for checking me out!!!

root gnome-terminal

share|improve this question

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

bumped to the homepage by Community♦ 53 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment | 

1

1

I'm using gnome on Debian Jessie. When I tried to close terminal after logged in as root, it told me like in the picture below.

What should I do to prevent this from happening again? Is it a bug??

Thanks for checking me out!!!

root gnome-terminal

share|improve this question

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

bumped to the homepage by Community♦ 53 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment | 

I'm using gnome on Debian Jessie. When I tried to close terminal after logged in as root, it told me like in the picture below.

What should I do to prevent this from happening again? Is it a bug??

Thanks for checking me out!!!

root gnome-terminal

share|improve this question

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

share|improve this question

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

share|improve this question

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

edited Oct 18 '15 at 21:31

Thomas Dickey

54.6k55 gold badges110110 silver badges185185 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

asked Jul 15 '15 at 8:54

Nguyễn Quốc PhongNguyễn Quốc Phong

1133 bronze badges

1 Answer
1

active

oldest

votes

0

Well there are processess running in your terminal from before you became root -- sudo (or su) and two bash (one for root, one for your normal user)... as well as any background-jobs (started with & or put in the background) in either shell. It's a fair warning, and it's good if you're about to accidently close a terminal.

If you exit root first (which you ought to), you don't get the warning. Even better, if you also exit the shell for your normal user. Just closing the terminal not only risk killing some running proccess you've forgot about, it also prevents the shell (bash) from saving things like command-history.

share|improve this answer

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Your last sentence is wrong: closing the terminal sends SIGHUP to the shell, and that does make it save the history. If you don't get the warning, then I think there's no larger risk of killing background tasks than when exiting the shell, but I'm not sure, it's possible that the set of processes that receive SIGHUP is different in some corner cases.
  
  – Gilles
  Jul 15 '15 at 22:52
  

  
  
  
  

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
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216113%2fwhy-gnome-terminal-tells-me-there-is-still-a-process-running-while-logged-in-a%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Well there are processess running in your terminal from before you became root -- sudo (or su) and two bash (one for root, one for your normal user)... as well as any background-jobs (started with & or put in the background) in either shell. It's a fair warning, and it's good if you're about to accidently close a terminal.

If you exit root first (which you ought to), you don't get the warning. Even better, if you also exit the shell for your normal user. Just closing the terminal not only risk killing some running proccess you've forgot about, it also prevents the shell (bash) from saving things like command-history.

share|improve this answer

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Your last sentence is wrong: closing the terminal sends SIGHUP to the shell, and that does make it save the history. If you don't get the warning, then I think there's no larger risk of killing background tasks than when exiting the shell, but I'm not sure, it's possible that the set of processes that receive SIGHUP is different in some corner cases.
  
  – Gilles
  Jul 15 '15 at 22:52
  

  
  
  
  

add a comment | 

0

Well there are processess running in your terminal from before you became root -- sudo (or su) and two bash (one for root, one for your normal user)... as well as any background-jobs (started with & or put in the background) in either shell. It's a fair warning, and it's good if you're about to accidently close a terminal.

If you exit root first (which you ought to), you don't get the warning. Even better, if you also exit the shell for your normal user. Just closing the terminal not only risk killing some running proccess you've forgot about, it also prevents the shell (bash) from saving things like command-history.

share|improve this answer

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Your last sentence is wrong: closing the terminal sends SIGHUP to the shell, and that does make it save the history. If you don't get the warning, then I think there's no larger risk of killing background tasks than when exiting the shell, but I'm not sure, it's possible that the set of processes that receive SIGHUP is different in some corner cases.
  
  – Gilles
  Jul 15 '15 at 22:52
  

  
  
  
  

add a comment | 

Well there are processess running in your terminal from before you became root -- sudo (or su) and two bash (one for root, one for your normal user)... as well as any background-jobs (started with & or put in the background) in either shell. It's a fair warning, and it's good if you're about to accidently close a terminal.

If you exit root first (which you ought to), you don't get the warning. Even better, if you also exit the shell for your normal user. Just closing the terminal not only risk killing some running proccess you've forgot about, it also prevents the shell (bash) from saving things like command-history.

share|improve this answer

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges

share|improve this answer

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges

answered Jul 15 '15 at 9:05

Baard KopperudBaard Kopperud

4,56844 gold badges2828 silver badges4646 bronze badges