Eagle makes important changes to the Network File System (NFS) configuration of your A Box and G Box with respect to NFS. It is important that you understand these changes and how they ensure the security of your system-and that you not override these changes. First, the Eagle installation turns off NFS server services for your G Box. This step ensures that no other system-not even your A Box can access NFS services from your G Box and prevents access to the important information stored in your Eagle logfiles.
Also, the installation enables NFS server services on your A Box, but strictly limits access to them for security purposes. The key to the security of the Eagle system is the security of your A Box and its authorization database. This file is physically stored on the A Box and NFS-exported for reading by the Eagle software on the G Box. The permissions for this NFS mount limit access to the authorization file to the G Box alone, and that in read-only mode. These limitations are absolutely critical to the security of your system and should not be changed in any way for any reason. It is very tempting, for example, to make this NFS mount read-write for the G Box to enable the system administrator to make changes in the authorization file from the G Box console. Don't do this. To ensure the security of your system, you should make changes to the authorization file only from the console of the A Box, and not through any other means.