<story><title>Mach&apos;s designers simply assumed that systems would be rebooted often enough</title><url>http://clozure.com/pipermail/openmcl-devel/2011-February/012567.html</url><text></text></story><parent_chain></parent_chain><comment><author>mobilemonkey</author><text>I&apos;m not going to pretend I know what Mach is, but around here, (big company that you&apos;re familiar with), rebooting/bouncing the servers is pretty much how issues are dealt with. &quot;Response times outside of SLA: bounced the server.&quot; &quot;Database connections timing out: bounced the server.&quot; &quot;Users experiencing high load times for pages: restarted JVMs. Then bounced the servers.&quot;&lt;p&gt;Root cause seems to be &quot;server up too long.&quot;</text></comment>
<story><title>Mach&apos;s designers simply assumed that systems would be rebooted often enough</title><url>http://clozure.com/pipermail/openmcl-devel/2011-February/012567.html</url><text></text></story><parent_chain></parent_chain><comment><author>jarin</author><text>I wonder if that&apos;s been fixed in the OS X/Darwin version of Mach, seems like the only time I ever reboot my MacBook is for system updates.</text></comment>