Proper way to shutdown OpenVAS
0
I currently start OpenVAS by calling openvasmd, ad, and sd manually. What is the proper way to stop these services? Killing the processes works but I don't know what might not be cleaned up by the abrupt termination.
kali-linux
migrated from security.stackexchange.com Sep 22 '14 at 7:59
This question came from our site for information security professionals.
add a comment |
0
I currently start OpenVAS by calling openvasmd, ad, and sd manually. What is the proper way to stop these services? Killing the processes works but I don't know what might not be cleaned up by the abrupt termination.
kali-linux
migrated from security.stackexchange.com Sep 22 '14 at 7:59
This question came from our site for information security professionals.
add a comment |
0
0
0
I currently start OpenVAS by calling openvasmd, ad, and sd manually. What is the proper way to stop these services? Killing the processes works but I don't know what might not be cleaned up by the abrupt termination.
kali-linux
I currently start OpenVAS by calling openvasmd, ad, and sd manually. What is the proper way to stop these services? Killing the processes works but I don't know what might not be cleaned up by the abrupt termination.
kali-linux
kali-linux
asked Sep 20 '14 at 17:58
caoimhin
migrated from security.stackexchange.com Sep 22 '14 at 7:59
This question came from our site for information security professionals.
migrated from security.stackexchange.com Sep 22 '14 at 7:59
This question came from our site for information security professionals.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
Did the installation create a service? Is there a reason you don't start it using the service mechanism, if so? I don't know what distro you're running so I can't specifically state how you'd stop and start the OpenVAS service, but I would look into that rather than manually launching the processes manually.
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f814903%2fproper-way-to-shutdown-openvas%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
0
Did the installation create a service? Is there a reason you don't start it using the service mechanism, if so? I don't know what distro you're running so I can't specifically state how you'd stop and start the OpenVAS service, but I would look into that rather than manually launching the processes manually.
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
add a comment |
0
Did the installation create a service? Is there a reason you don't start it using the service mechanism, if so? I don't know what distro you're running so I can't specifically state how you'd stop and start the OpenVAS service, but I would look into that rather than manually launching the processes manually.
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
add a comment |
0
0
0
Did the installation create a service? Is there a reason you don't start it using the service mechanism, if so? I don't know what distro you're running so I can't specifically state how you'd stop and start the OpenVAS service, but I would look into that rather than manually launching the processes manually.
Did the installation create a service? Is there a reason you don't start it using the service mechanism, if so? I don't know what distro you're running so I can't specifically state how you'd stop and start the OpenVAS service, but I would look into that rather than manually launching the processes manually.
answered Sep 20 '14 at 18:35
theterribletrivium
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
add a comment |
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
I'm using it on Kali. No service was created in the way I think you mean. It runs as a daemon but there is no System V init script that allows it to be controlled by the service command. All references to OpenVAS either use their own bash script to start it or just discuss the methods I've already mentioned.
– caoimhin
Sep 22 '14 at 0:27
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Here's an example. I do the same as this guy but I'd rather know if there is an approved way to shut it down other than killing it. backtrack-linux.org/forums/showthread.php?t=58547
– caoimhin
Sep 22 '14 at 0:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood uses kill as shown here:
– theterribletrivium
Sep 22 '14 at 6:29
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
Yikes, I hit enter before I was finished editing and apparently by the time I finished I am unable to edit it. Anyway, here is what I meant to type: Using kill is typically acceptable as Linux programs are supposed to be designed to receive that signal and shut down cleanly. Avoid using any more forceful kill signals such as -9, and you should be okay. Just to test this I installed openvas in CentOS and the service under the hood calls a function called killproc from /etc/init.d/functions. Killproc actually uses kill with the default flag as shown here: kill -TERM $pid >/dev/null 2>&1
– theterribletrivium
Sep 22 '14 at 6:44
add a comment |
draft saved
draft discarded
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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f814903%2fproper-way-to-shutdown-openvas%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
