> <span style="line-height: 18px;">This works fine if I do it manually
while SSH’ed into the Rancid server</span><div><span style="line-height: 18px;">> but if I run it through cron the ssh
instances hang.</span><blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div lang="EN-US" link="blue" vlink="purple"><div>
</div>
</div>
</blockquote></div><div><span style="line-height: 18px;"><br></span></div><div><span style="line-height: 18px;">I don't run rancid, but I have some homegrown stuff I maintain that works in a similar fashion.</span></div><div><span style="line-height: 18px;">In general I look for differences in the execution environment. </span></div><div><span style="line-height: 18px;"> - Dump the environment to look for changes in the path, etc.<br> - If you are running as a different user, look for permissions issues.</span></div><div><span style="line-height: 18px;"> - maybe you cannot find your .cloginrc or some executable you are shelling out to.</span></div><div><span style="line-height: 18px;"> - Non-interactive shells behave differently than interactive shells in terms of sourcing dotfiles and more.</span></div><div><span style="line-height: 18px;"> You can force them to be treated as interactive, but if you have something expecting something on STDIN,</span></div><div><span style="line-height: 18px;"> you are going to be waiting for a long time. <br><br>Have you tried enabled debugging using debug and exp_internal? It can be real handy when expect is waiting on a pattern match, and you need to see exactly what it is waiting on.<br><br><br><br></span></div><div><span style="line-height: 18px;">Elle</span></div>