[ Comments below, in-line ] On 04/04/2012 10:20 AM, Phil Schaffner wrote:
Hi Phil, > The tech who ran the diagnostics has moved on, so I decided to do it > myself to verify. Excellent! > The begins the strange chain of events. :-) Well, I'm not a Mac person ... :) ... so ... I'm assuming the panic report request was due an error found before boot-up. It's clear there are no memory issues. Easy to rule out and now we don't have to worry about it. Given everything is running fine at the moment, there's not much to do until a problem arises. If I were in your situation, I'd `tail -f' against the VBox log and in another terminal, against the system log (/var/log/messages or equivalent). This way you can spot when a problem happens. I'm sorry I'm not much help ... "no se habla Mac" :) Cheers, -- Pablo Sanchez - Blueoak Database Engineering, Inc Ph: 819.459.1926 Blog: http://pablo.blog.blueoakdb.com Fax: 760.860.5225 (US) ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
