I work on a distributed application, and have been tasked with a feature
that lets users start all of our processes on a set of configured machines
from one 'master' box. The options I'm looking at now are rsh vs. inetd.
inetd gives greater control (rsh lets you run any command, while with inetd
I can ensure only my scripts are executed) at the cost of more complexity
(writing what is still a simple script kicked off by inetd instead of the
rsh one-liner, and handling authentication ourselves instead of relying on
the OS). inetd is more difficult to administrate, but not by much. So, if
customers wouldn't mind enabling/configuring rsh, I'd rather go that route,
because it's easier.
Not being an expert, I'm aware that there's many other issues regarding
starting distributed apps, but the main question I'm concerned about here
is: would a network-savvy customer object to our app using rsh?