I will be running several judgehosts in an environment where the OS image is coming from a flash drive. NFS is also available to the contest server. It looks like several of the judgehost directories (judgings, log, run, and tmp) create sub-directories by hostname and could therefore be shared over NFS. Is there any documentation that describes the best practices for doing that? I read through the administration manual but didn't see anything specifically addressing that topic.
Marc
Hi,
*Marc Furon marcf@dslextreme.com [15/11/13]:
I will be running several judgehosts in an environment where the OS image is coming from a flash drive. NFS is also available to the contest server. It looks like several of the judgehost directories (judgings, log, run, and tmp) create sub-directories by hostname and could therefore be shared over NFS. Is there any documentation that describes the best practices for doing that? I read through the administration manual but didn't see anything specifically addressing that topic.
We also use NFS for our contests, however a bit different.
The server exports the same installation *readonly* to all clients (teams and judgehosts). Then we use an union fs to make that image writable for the clients' OS. Of course, every user (teams and judgehost) gets a writable home exported from the NFS server.
We decided not to put the judgedaemons output directory in the NFS home because we didn't want to slow down submissions because of network latency and such stuff. So, the output directory lives in tmpfs and after each judging, we move that part of the output directory to the NFS server (for backup).
Tobi