<div>I also find it very odd.</div><div><br></div>2011/11/10 Hamish <span dir="ltr"><<a href="mailto:hamish_b@yahoo.com" target="_blank">hamish_b@yahoo.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>so it's fully reproducible?</div></blockquote><div>So far, yes. I've reproduced it three times, sadly twice by accident.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and the location still exists on the disk after you exit grass<br>
completely? (double check with `ps`, look for Init.sh)<br></blockquote><div>I just tried it this time again. ps -A | grep Init.sh turns up with nothing.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and it is gone directly after reboot? ie before grass is restarted<br>
after a boot?<br></blockquote><div>Yes.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
plenty of free disk space?</blockquote><div>Several hundred GB.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">e2fsck comes up clean?</blockquote><div>
Never worked with e2fsck before and it looked a little dangerous when I thumbed through the man page... Sadly, I'm kind of short on time today so I can't read myself into it too much. What are you looking for exactly?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ssd or traditional hard drive? </blockquote><div>Normal, traditional hard drive.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">anything special about the<br>
partition? (it's not symlinked into /var/tmp/ or anything like<br>
that?)<br></blockquote><div>Nope.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
does running "sync" before shutting down help?<br></blockquote><div>Tried it just now. Didn't make a difference.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
waiting >35 sec after shutting down grass before turning off the<br>
computer?<br></blockquote><div>Had done that every time before... I shut down GRASS, then finished some other projects, then turned off the computer so at least 20 minutes went by.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
grass itself doesn't go near the boot/shutdown init scripts<br>
so if it happens outside of grass I'm wondering what it could<br>
be..<br></blockquote><div>Yes, it definitely is strange, because it's always the location I worked on last.</div><div><br></div><div>I should perhaps mention that I also have GRASS 7 compiled from source, and I've worked with both versions on this machine before. However, the phenomenon I'm talking about right now has occured with GRASS 6, I haven't used 7 in at least three weeks. </div>
</div>