+--- In a previous state of mind, "Kelly Setzer" setzer@telalink.net wrote: | | For commands that can be done via rsh from the admin server, you only need to | a shell like bash or tcsh. I'm sure you know that, I only mention it because I
Yeah, I simply prefer to do my work on the filer. Allowing rsh is something I would really like to get away from. ssh on the filer would be a nice addition.
| What is the reasoning behind which commands will work via rsh and which | won't?
I don't know what the exact criteria is, but it looks like, for the most part. only commands that would be real bad are excluded. Sure, you can do bad things with some of the stuff (reboot, raid, halt, etc) but not as bad as what you could do with ifconfig, arp, nfs, setup or license.
alcatraz:8% sudo rsh maytag ? cifs df dump exportfs halt httpstat mt netstat nfsstat options raid reboot quota rdate restore route snap snmp sysconfig sysstat timezone uptime version ypwhich alcatraz:9%
vs:
? arp cifs date df download dump exportfs halt help hostname httpstat ifconfig license maxfiles mt ndmpd netstat nfs nfsstat options passwd ping raid reboot quota rdate restore route routed savecore setup shelfchk snap snmp sysconfig sysstat timezone uptime version ypwhich
setting some unsuspecting person's license to DISABLED might take a while to figure out :)
Perhaps the filers should not allow you to disable the remaining protocol (as a safety net).
Alexei