On Wed, Jun 14, 2000 at 01:01:42AM -0700, Bruce Sterling Woodcock wrote:
And there's often a very good reason why not. Using this to "get
around"
non-rshable command limitations can compromise your filer and lead to many crashes.
it can and has often saved me from having to track down who is telnetted in when for some reason the console port is unavailable. also on my older filers our operators telnet in to kick off backups. if for some reason i need to run commands on the filer this is the only way.
These are all administrative issues, however. The backups could be run by rsh or other means. You could also run only the rsh-safe commands on the filer.
i haven't yet had a filer crash due to running commands via rsh. knowing that this option is available is useful, but as with any operation on the filer, sure, it has the potential to crash the machine.
It has a greater potential to crash the machine because there's a reason those commands aren't rsh-able.
It's possible in a future release that running those non-rshable commands through rsh via rc_toggle_basic will cause a crash every time, or it will report false data which then results in your doing the wrong thing. If you are aware of these risks and will only blame yourself, fine, but I would not want to risk it if it can be avoided.
Bruce