Hi all
Thanks for the replies so far, most helpful. Just a few responses:
On 05 January 2006 17:48, Michael Bergman wrote:
Well, I assume you do have the /etc/ directory (or rather the root volume, in many cases called vol0) NFS-exported to at least one NFS-client already. How else do you administer the filer when you work with it manually?
Actually, so far (15 months of production use) I haven't yet had much cause to deal with the filer outside of the web admin interface or via a console/telnet/ssh session. All the problems I've experienced, and all the configuration I've had to do, have been achievable that way - so I haven't had much cause to mount /vol/vol0 onto remote hosts apart from a few occasions where I had to grab core dumps or logfiles for debugging.
I had, of course, rather idiotically forgotten the rsh/ssh way. Hence "dumb question" :)
On 05 January 2006 17:49, Skottie Miller wrote:
the quota files are editied from the admin host, which has <ROOT>/etc mounted. then we "rsh <FILER> quota resize" so changes take effect.
On 06 January 2006 10:56, Neis, Mark wrote:
If NFS-exporting /etc ist what you want to prevent, you could script it using SSH to remotely execute filer commands:
[snip]
Again, I'd missed the rsh/ssh option; the reason for trying to avoid having /vol/vol0 mounted anywhere is one of security. I suppose it could be done in a mount/edit/rsh/commit/unmount procedure, but the likely rate of change is such that we may simply have to harden a host in the platform to do the admin tasks and mount the volume there.
Thanks for all the advice, I've opened my eyes again now and have a way forward :)
Graeme