<div>All,</div>
<div> </div>
<div>Removing the dods_cache directory seemed to cure the problem.</div>
<div> </div>
<div>Thanks!</div>
<div> </div>
<div>Dan<br><br> </div>
<div><span class="gmail_quote">On 1/12/06, <b class="gmail_sendername">Jennifer Adams</b> <<a href="mailto:jma@cola.iges.org">jma@cola.iges.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Jan 12, 2006, at 4:15 PM, Patrice Dumas wrote:<br><br>> On Thu, Jan 12, 2006 at 04:09:30PM -0500, Jennifer Adams wrote:
<br>>> You may have a corrupted file in your $HOME/.dods_cache/ directory.<br>>> Try<br>>> removing the whole directory and see if that helps.<br>><br>> That's pretty annoying if a corrupted file may lead to a segfault, it
<br>> opens<br>> the door for a security break... Is it a known bug of old dods<br>> libraries?<br>I don't know whether it's a known bug or even if it's the result of<br>'operator error' rather than software problems. All I know is that now
<br>and then clearing the local cache can resolve problems that other<br>troubleshooting protocols don't fix.<br><br>Jennifer<br><br>--<br>Jennifer Miletta Adams<br>Center for Ocean-Land-Atmosphere Studies (COLA)<br>4041 Powder Mill Road, Suite 302
<br>Calverton, MD 20705 USA<br><a href="mailto:jma@cola.iges.org">jma@cola.iges.org</a><br></blockquote></div><br>