SIGHUP for reloading configuration
According to signal(7) , SIGHUP is used to detect hangup on controlling terminal or death of controlling process. However, I have come across a lot of OSS daemons(services) where SIGHUP is used to initiate a reload of configuration. Here are a few examples: hostapd , sshd , snort etc. Is this a standard(or a generally acceptable) way to implement a reload? If not, whats recommended? SIGHUP as a notification about terminal closing event doesn't make sense for a daemon, because deamons are detached from their terminal. So the system will never send this signal to them. Then it is common practice