Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
how to generate SIGHUP signal? In which case signal generation gets failed?
Read the "Question Guidelines" link in my posting signature; unless you provide details and ask a clear question, there's little we can do to help you. Also, doing basic research first before posting is a good thing. https://en.wikipedia.org/wiki/SIGHUP
A sighup can be MANY different things, depending on the terminal, shell, program, language, or what the programmer has DECIDED it needs to be.
A minor addition to chrism01's post is that either using the library function call kill(2), or the command line call for kill(1), you do not have to send just SIGKILL, you can send any of the signals. I believe (didn't double check) that there is also just a signal(2) library call which does the same thing, just appears clearer due to the name, and I think part of both the kill call options are only that since SIGKILL is so common, they made that the default.
I'm not that historical with Unix or System V if that's where it originated, but ran into someone using code to send a different signal other than KILL but still using the kill() function. It confused me until I looked up the man page for kill.
Figure out if you're using a function call or the command line and then chose your option to send the signal.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.