Unsolved
This post is more than 5 years old
15 Posts
0
1702
January 20th, 2015 06:00
How to restart nsrexec on NW server (Linux) without restarting nsrd
Hi,
how to restart nsrexec deamon without completely restarting NetWorker server. I made some changes to the servers file and I'm not able to restart the whole NetWorker...
Thanks
René
No Events found!
crazyrov
4 Operator
•
1.3K Posts
0
January 20th, 2015 06:00
nsrexecd is a dependent daemon for nsrd to run. Even if you do succeed in getting it done i dont that the nsrd will be in a stable state after the restart of just the nsrexec.
ble1
4 Operator
•
14.3K Posts
0
January 20th, 2015 06:00
Not possible (I don't think HUP works with nsrexecd).
renealbrecht
15 Posts
0
January 20th, 2015 06:00
It is and I did know how... But I forgot it.
bingo.1
2.4K Posts
0
January 20th, 2015 09:00
By running "ps -ef | grep nsr" you would be able to verify the process dependencies.
If you kill nsrexecd (not the recommended way) you will see that the other nsr processes will also be killed.
renealbrecht
15 Posts
0
January 21st, 2015 01:00
Yeah... I know, that server processes like nsrd are depending from nsrexec deamon. I don't want to restart the nsrexec, instead I "simply" want to force it to reload it's config (like servers file). I tried to kill -SIGHUP, because I found SIGHUP in strings of nsrexec and thought it was handled to reload it's config - but nsrexec was not responding after killing it via SIGHUP signal.
oldhercules
1 Rookie
•
116 Posts
0
January 21st, 2015 03:00
(I don't know the solution, just a small remark: SIGHUP must be handled in a program at least to be able to ignore it. If it's not handled the program will be terminated by default).
renealbrecht
15 Posts
0
January 21st, 2015 05:00
How I mentioned: One of the strings in nsrexec is "SIGHUP", so I thought nsrexec would be able to handle SIGHUP to reload config informations.