On Mon, Jan 18, 2010 at 8:48 PM, steve klise <span dir="ltr">&lt;<a href="mailto:klises@caminomedical.org">klises@caminomedical.org</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>--snip--<br>
rsh to your filer with the output<br>
rsh &lt;filername&gt; cifs shares -add &lt;name of share&gt; /vol/volume_for_your_share/<br> --snip--</blockquote><div><br></div><div>I would be very, very careful with using rsh. It&#39;s very insecure. ssh via either the standard unix ssh command, or plink, can be used as a drop in replacement, and is much, much more secure. </div>
<div><br></div><span class="Apple-style-span" style="font-family: Times; font-size: medium; "><li>ssh authorized_keys (passwordless ssh): <a href="http://www.nabble.com/ssh-config-on-DOT-7-t2595957.html">http://ww w.nabble.com/ssh-config-on-DOT-7-t2595957.html</a></li>
<li>ssh inline replacement of rsh on a unix host: <a href="http://www.didc.lbl.gov/DPSS/ssh-info.html">http://www.didc. lbl.gov/DPSS/ssh-info.html</a></li></span><div> </div><div>If you *do* have to use rsh, be sure to use role based access controls to create a user, and a role w/ minimum number of commands needed. </div>
</div>