Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Hi I am trying to run a script/runner process which failed because of SignalException: SIGHUP:
The process nearly takes 4-5hrs. Can someone please let me know what exactly is happening and what would be a work around.
Thanks
The shell the process was started from is dying. You can either disown the process from the calling shell or call it with
nohup, which will cause the process to ignore SIGHUPs.Something like
nohup script/runner "YourCodeHere.run" &would make the script/runner task impervious to SIGHUPs.Edit: Say you ssh into a server. You’ll spawn a new shell (running /bin/bash would work similarly). If you drop connection, the shell you started with ssh also dies. When it does, it sends SIGHUP to all of the attached processes. SIGHUP is a UNIX signal. There are a few of them. Another you’re probably (perhaps unknowingly) familiar with is SIGINT, which is what is sent to the process when you hit ctrl-c.