On 30May2013 14:41, derek martin <[email protected]> wrote: | On Thu, May 30, 2013 at 01:45:47PM -0400, Patrick Shanahan wrote: | > * jack <[email protected]> [05-30-13 12:14]: | > > I have noticed that when I do this, eventually I return to find | > > that my ssh connection is still open and working fine, but mutt | > > has quit. The prompt says: | > > | > > Caught signal 15... Exiting. | > > Is this a bug? What does "signal 15" mean? | [...] | > | > Just guessing but I would say you are timing out the ssh connections | > rather than mutt. | | He's already said that the SSH sessions remain connected, only mutt | has been killed (relevant bit quoted above). | | To answer the question, signal 15 = SIGTERM, which is what happens | when you press CTRL-C (the terminal driver sends a TERM[inate] signal | to the active process, usually allowing it to die gracefully).
No, it is not. Ctrl-C normally sends SIGINT to the front process group (which will be mutt). SIGTERM has a similar effect, but is a different signal; it is the normal signal one would send to terminate a process. | You | can also send this signal with the kill command, e.g.: | | $ ps aux |grep '[m]utt' | demartin 21019 0.0 0.1 29440 4208 pts/5 S+ May23 0:10 mutt | $ kill -TERM 21019 | | You should contact the people running the box you rent, and see if | they have some watchdog process that kills processes which have been | running too long. That would be my guess too. Maybe they kill the front process (or process group) on idle interactive terminals. Cheers, -- Cameron Simpson <[email protected]> The least pain in our little finger gives us more concern and uneasiness than the destruction of millions of our fellow human beings. - William Hazlitt, Works, Vol.X
