You will need to create a file for Zope to write to. If you try to ftp in, and there's no file for Zope to write to, it will crash. I know from experience. Check the Zope.org documentation and search for nohup. You just need to modify your start script. Michael On Wed, 2002-09-18 at 13:19, Rudi asn wrote:

I'm trying to set up a webserver on a Redhat 7.2 Intel server. At first I installed Zope 2.3 . Every time I tried to ftp to the server, the zope server crashed. Looking at zope.org, I found I should look for the correct python version and upgrade to zope 2.5. Now I got zope 2.5.1 installed. Whenever I am working at www.server.at/manage (for example creating a new user or a new folder) the server crashes and I have to reboot the whole system. Not only zserver crashes, the Redhat 7.2 crashes (no access with the console or network).

I never(!!) experienced, that a linux computer crashes completely, I always thought only windows computer do this. My question: Does this look like a hardware problem (memory chips ?) or did anyone experience a similar problem?

Ladinig Rudi Borg Innsbruck mail: r.ladinig@asn-ibk.ac.at

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

Rudi asn writes:

... Now I got zope 2.5.1 installed. Whenever I am working at www.server.at/manage (for example creating a new user or a new folder) the server crashes and I have to reboot the whole system. Not only zserver crashes, the Redhat 7.2 crashes (no access with the console or network).

I never(!!) experienced, that a linux computer crashes completely, I always thought only windows computer do this. Something seems to be quite wrong with your system.

Check the log files (usually located under "/var/log" or "/var/adm").

My question: Does this look like a hardware problem (memory chips ?) I would be surprised if it were are hardware problem. It is too deterministic for that. I expect some software problem and hope you will find some indications in a (Linux) log file.

Dieter