For production servers, you probably want each ZEO client and the ZEO server to be started when the system is booted. The exact procedure will vary depending on the operating system, but in general a startup script should run
bin/zeoserver start and the equivalent commands for the ZEO clients to start these in daemon mode.
On Windows, each Zope instance can be installed as a Windows service, managed from the Services control panel. For example, this will install the primary instance as a service that is automatically started:
> bin\primary --startup=auto install
Note that the ZEO server still needs to be started as a standalone process.
For security reasons, you can let Zope assume the identity of a particular user when it runs. ...