x11vnc server - creating multiple zombie processes - how do I stop it?












1















Recently started using x11vnc server on Ubuntu (10.04) for remote access over internet from win$ PC using SSL/SSH vnc viewer.



Thought I had it config'd ok then noticed many zombie processes for x11vnc, like 20+ in sys monitor sometimes.



I'm using terminal cmd: x11vnc -rfbversion 3.6 -rfbport 5900 -rfbauth /home/xxxx/.vnc/passwd -forever -bg -gui tray to start it.



How can I stop/avoid it creating the zombies every connect/disconnect?










share|improve this question
















bumped to the homepage by Community 9 mins ago


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
















  • After you have finished with x11vnc, pkill x11vnc might work.

    – Wilf
    Dec 3 '13 at 16:38













  • won't this kill x11vnc for future connections? This is an unattended pc which i need x11vnc to be running at all times. thanks for the interest.

    – CJ_Snr
    Dec 4 '13 at 11:57
















1















Recently started using x11vnc server on Ubuntu (10.04) for remote access over internet from win$ PC using SSL/SSH vnc viewer.



Thought I had it config'd ok then noticed many zombie processes for x11vnc, like 20+ in sys monitor sometimes.



I'm using terminal cmd: x11vnc -rfbversion 3.6 -rfbport 5900 -rfbauth /home/xxxx/.vnc/passwd -forever -bg -gui tray to start it.



How can I stop/avoid it creating the zombies every connect/disconnect?










share|improve this question
















bumped to the homepage by Community 9 mins ago


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
















  • After you have finished with x11vnc, pkill x11vnc might work.

    – Wilf
    Dec 3 '13 at 16:38













  • won't this kill x11vnc for future connections? This is an unattended pc which i need x11vnc to be running at all times. thanks for the interest.

    – CJ_Snr
    Dec 4 '13 at 11:57














1












1








1








Recently started using x11vnc server on Ubuntu (10.04) for remote access over internet from win$ PC using SSL/SSH vnc viewer.



Thought I had it config'd ok then noticed many zombie processes for x11vnc, like 20+ in sys monitor sometimes.



I'm using terminal cmd: x11vnc -rfbversion 3.6 -rfbport 5900 -rfbauth /home/xxxx/.vnc/passwd -forever -bg -gui tray to start it.



How can I stop/avoid it creating the zombies every connect/disconnect?










share|improve this question
















Recently started using x11vnc server on Ubuntu (10.04) for remote access over internet from win$ PC using SSL/SSH vnc viewer.



Thought I had it config'd ok then noticed many zombie processes for x11vnc, like 20+ in sys monitor sometimes.



I'm using terminal cmd: x11vnc -rfbversion 3.6 -rfbport 5900 -rfbauth /home/xxxx/.vnc/passwd -forever -bg -gui tray to start it.



How can I stop/avoid it creating the zombies every connect/disconnect?







server vnc






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 3 '13 at 20:00









BuZZ-dEE

9,225115169




9,225115169










asked Dec 3 '13 at 16:32









CJ_SnrCJ_Snr

612




612





bumped to the homepage by Community 9 mins ago


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







bumped to the homepage by Community 9 mins ago


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















  • After you have finished with x11vnc, pkill x11vnc might work.

    – Wilf
    Dec 3 '13 at 16:38













  • won't this kill x11vnc for future connections? This is an unattended pc which i need x11vnc to be running at all times. thanks for the interest.

    – CJ_Snr
    Dec 4 '13 at 11:57



















  • After you have finished with x11vnc, pkill x11vnc might work.

    – Wilf
    Dec 3 '13 at 16:38













  • won't this kill x11vnc for future connections? This is an unattended pc which i need x11vnc to be running at all times. thanks for the interest.

    – CJ_Snr
    Dec 4 '13 at 11:57

















After you have finished with x11vnc, pkill x11vnc might work.

– Wilf
Dec 3 '13 at 16:38







After you have finished with x11vnc, pkill x11vnc might work.

– Wilf
Dec 3 '13 at 16:38















won't this kill x11vnc for future connections? This is an unattended pc which i need x11vnc to be running at all times. thanks for the interest.

– CJ_Snr
Dec 4 '13 at 11:57





won't this kill x11vnc for future connections? This is an unattended pc which i need x11vnc to be running at all times. thanks for the interest.

– CJ_Snr
Dec 4 '13 at 11:57










2 Answers
2






active

oldest

votes


















0














Running pkill x11vnc should stop x11vnc plus any zombie processes it creates.



This will just send the signal SIGTERM for the program to terminate, and you will be able to run x11vnc after pkilling the previous instance of it.






share|improve this answer
























  • as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

    – CJ_Snr
    Dec 4 '13 at 17:31











  • Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

    – Wilf
    Dec 4 '13 at 17:40



















0














There is a way to clean all hung sessions



`x11vnc -clear-all`





share|improve this answer


























  • That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

    – josh2112
    Nov 3 '15 at 14:48













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f385527%2fx11vnc-server-creating-multiple-zombie-processes-how-do-i-stop-it%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Running pkill x11vnc should stop x11vnc plus any zombie processes it creates.



This will just send the signal SIGTERM for the program to terminate, and you will be able to run x11vnc after pkilling the previous instance of it.






share|improve this answer
























  • as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

    – CJ_Snr
    Dec 4 '13 at 17:31











  • Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

    – Wilf
    Dec 4 '13 at 17:40
















0














Running pkill x11vnc should stop x11vnc plus any zombie processes it creates.



This will just send the signal SIGTERM for the program to terminate, and you will be able to run x11vnc after pkilling the previous instance of it.






share|improve this answer
























  • as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

    – CJ_Snr
    Dec 4 '13 at 17:31











  • Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

    – Wilf
    Dec 4 '13 at 17:40














0












0








0







Running pkill x11vnc should stop x11vnc plus any zombie processes it creates.



This will just send the signal SIGTERM for the program to terminate, and you will be able to run x11vnc after pkilling the previous instance of it.






share|improve this answer













Running pkill x11vnc should stop x11vnc plus any zombie processes it creates.



This will just send the signal SIGTERM for the program to terminate, and you will be able to run x11vnc after pkilling the previous instance of it.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 4 '13 at 16:54









WilfWilf

21.4k1067129




21.4k1067129













  • as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

    – CJ_Snr
    Dec 4 '13 at 17:31











  • Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

    – Wilf
    Dec 4 '13 at 17:40



















  • as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

    – CJ_Snr
    Dec 4 '13 at 17:31











  • Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

    – Wilf
    Dec 4 '13 at 17:40

















as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

– CJ_Snr
Dec 4 '13 at 17:31





as I said, this is an unattended pc, how would I restart x11vnc when I cannot access the remote pc, x11vnc has been killed?

– CJ_Snr
Dec 4 '13 at 17:31













Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

– Wilf
Dec 4 '13 at 17:40





Either A) ignore the zombie processes, they are probably x11vnc itself anyway B) Create a bash script to execute it a certain times etc. Ignoring 'em may be best.

– Wilf
Dec 4 '13 at 17:40













0














There is a way to clean all hung sessions



`x11vnc -clear-all`





share|improve this answer


























  • That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

    – josh2112
    Nov 3 '15 at 14:48


















0














There is a way to clean all hung sessions



`x11vnc -clear-all`





share|improve this answer


























  • That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

    – josh2112
    Nov 3 '15 at 14:48
















0












0








0







There is a way to clean all hung sessions



`x11vnc -clear-all`





share|improve this answer















There is a way to clean all hung sessions



`x11vnc -clear-all`






share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 7 '14 at 13:48









Elder Geek

26.7k953127




26.7k953127










answered Dec 7 '14 at 6:24









Carlos Alberto Solis MadrigalCarlos Alberto Solis Madrigal

1




1













  • That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

    – josh2112
    Nov 3 '15 at 14:48





















  • That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

    – josh2112
    Nov 3 '15 at 14:48



















That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

– josh2112
Nov 3 '15 at 14:48







That's not at all what this does. First, it's --clear_all, with 2 dashes and an underscore. Second, this option doesn't clear defunct sessions, it tells the x11vnc server to explicitly release the modifier keys (shift, ctrl, numlock, etc.) when entering and exiting the session to prevent any of them from getting stuck on.

– josh2112
Nov 3 '15 at 14:48




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f385527%2fx11vnc-server-creating-multiple-zombie-processes-how-do-i-stop-it%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

GameSpot

connect to host localhost port 22: Connection refused

Getting a Wifi WPA2 wifi connection