Chris's Wiki :: blog/linux/UbuntuVarRun Commentshttps://utcc.utoronto.ca/~cks/space/blog/linux/UbuntuVarRun?atomcommentsDWiki2008-06-30T13:05:55ZRecent comments in Chris's Wiki :: blog/linux/UbuntuVarRun.From 84.16.37.165 on /blog/linux/UbuntuVarRuntag:CSpace:blog/linux/UbuntuVarRun:8ca007eb8af644bcb68592c8e2249f27a4186aedFrom 84.16.37.165<div class="wikitext"><p>Thanks for this info!</p>
<p>-- Salutis</p>
</div>2008-06-30T13:05:55ZFrom 202.6.116.238 on /blog/linux/UbuntuVarRuntag:CSpace:blog/linux/UbuntuVarRun:97f24851a83d68ab6243d97b653045ed700e98dbFrom 202.6.116.238<div class="wikitext"><p>Mate, we have been banging our heads on this problem for ages with some Xen virtual machines running Dapper - thank you HEAPS for posting this fix- worked for us, too. We shifted from VMs with a single filesystem (containing /var and its contents) to VMs mounting a root, /var, and /home filesystems. Simply shifting the /var dir (which had content in it from the previous configuration) to var-old, creating a new /var with empty /var/run and /var/lock directories in it worked a treat. </p>
<p>All the best from New Zealand,</p>
<p>Dave (at egressive.com)</p>
</div>2007-08-22T00:40:23ZFrom 66.92.1.117 on /blog/linux/UbuntuVarRuntag:CSpace:blog/linux/UbuntuVarRun:cf9721a5359915c50efd02ced5204167268f07daFrom 66.92.1.117<div class="wikitext"><p>Phew! Thanks for pointing that out. We have run into the same problem too!</p>
</div>2007-02-15T01:42:49Z