-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Bo M. Maryniuck Sent: Wednesday, February 12, 2003 2:47 AM To: Dieter Maurer Cc: zope@zope.org Subject: Re: [Zope] Zope 2.6.1 Released
On Monday 10 February 2003 21:40, Dieter Maurer wrote:
Your environment decides to send Zope a SIGHUP signal (signal 1). It is correct that Zope dies on this signal. Unix operating systems usually send a SIGHUP signal when the control terminal is closed. The command "nohup" (--> "man" pages) is usually used to cope with this fact....
Dieter, I know what SIGHUP and "man" pages means since I dont know what "MS Windows" and "Microsoft" is. ;-) OTOH, it is not quite correct since I start it with nohup and ampersand "&" in my /etc/init.d/zope script. And it even does not crashes when weather is quite ok. ;-) For example, I'm happy already third day: Zope still works, but I'm sitting like on a bomb -- when it will crash next time?
Dieter's point is that neither the program nor the OS will autogenerate a sig hup. HUP is not like a segv that signals a program fault. Something external to zope is to blame for your sig hup. Most often, this is caused by people not reading the man page for nohup. PS. Please post in ASCII only.