"James M. Slack" wrote:

I finally got Zope2 running by supplying the IP address with -a: start -a 127.0.0.1

At first I didn't think it was working, because I didn't see any confirmation message -- it just appeared to hang. (On my Linux machine at work, I get a rather detailed message showing the ports in use, etc.) Everything seems to work otherwise, so I guess I'm happy.

The behaviors of windows and UNIX are quite different and controled by two different aspects of Zope in terms of process launching. In UNIX, zdaemon.py handles everything, in Windows, I believe it's ZService.py. -Michel

Thanks for your help...

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce

For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )

In article <Pine.LNX.4.10.9907261529190.2595-100000@orion.cs.mankato.msu s.edu>, James M. Slack <slack@orion.cs.mankato.msus.edu> writes

At first I didn't think it was working, because I didn't see any confirmation message -- it just appeared to hang. (On my Linux machine at work, I get a rather detailed message showing the ports in use, etc.) Everything seems to work otherwise, so I guess I'm happy.

I was confused too. 1.11pr1 also used to give a detailed message under win32 with zserver, but not so with 2b1. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz