Bill Anderson wrote:

Michael Bernstein wrote:

...

I have successfully installed and compiled Zope 2.0.0a1 on my home machine, but cannot seem to get it to start. I believe that the reason is that it's connection to the net is a cable-modem, and it's using DHCP.

Has anyone else encountered this? I've succesfully installed Zope 2.0 on another machine with a static IP address at work.

BTW, I am not so concerned about making this installation externally accessible (though it would be nice), but mainly want to do development at home as well.

What port are you trying to use? If ==80, you have two issues: you would need to be root, and youe would have to turn off apache (on by default in rehdat installs). I use it with a dhcp address just fine (even on my production servers).

Actually there was a port 80 bug, as described in this post to another thread:

...

Ok, I realize I am probably exposing myself as a Linux newbie, but Zope will not start up on port 80. I realize this is because of some sort of security measure, as Zope is running as the user nobody, and Linux does not give anyone other than root the ability to assign ports lower than 1024.

How do I get around this? I need to access this system through a firewall without letting any more ports through.

This is a bug now fixed in the CVS. The startup script first switches to user nobody, and then tries to bind to port 80, a privileged port. The latest version in the CVS reverses this.

But the problem I described here turned out to be my own fault, as I had a hostname conflict, which was causing socket.gethostbyname to barf. Cheers, Michael Bernstein.