If you want to share filesystem content between a set of ZEO clients that are running on separate machines, you will need to set up something like NFS or maybe Samba or another mountable network file system on each client. Then you will need to export a directory from a "central" location that can be mounted by each client. We use NFS sometimes for this, and one tip is to put the export on one client as something like /home/zope/share and mount it on every other client as the same name. Then you can address the files that go in the share the same from any machine. It also helps to actually put the Zope software home in a mounted filesystem so all of your clients share the same Zope code. This is generally required for ZEO and it's a reasonable way to accomplish it. HTH, - C ----- Original Message ----- From: "Schmidt, Allen J." <aschmidt@nv.cc.va.us> To: <zope@zope.org> Sent: Friday, March 15, 2002 9:44 AM Subject: [Zope] ZEO and LocalFS

If we have ZEO (and other ZEO Zope clients) on a different box from our primary clients, how does that affect LocalFS? How does the path figure into that? Will FNS need to be setup and all the paths for each client point back to one central file system storage location? Just curious before we start spreading things out.

Thanks

Allen

_______________________________________________ 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 )