On Mon, 20 Feb 2017, Dan McDonald wrote:
; a.) Accept "-r" as a requirement, and document to users that the behavior
between 014-020 and 022-beyond will change.
This one gets my vote. It will actually improve our workflow here!
Andy
--
Citrus IT Limited | +44 (0)870 199 8000 |
This is not normal. Do you have a crash dump available, or at least a panic
string?
/dale
> On Feb 21, 2017, at 10:57 AM, Linda Kateley wrote:
>
> Has anyone run into omnios panicing in virtualbox?
>
> I have been working on a video series of napp-it and when I put them
Great. I'll make sure this gets back into at least 020, and hopefully it'll
easily drop into 014 as well.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Feb 21, 2017, at 4:19 PM, Michael Talbott wrote:
>
> Dan, the updated driver that you provided did fix the
Dan, the updated driver that you provided did fix the issue I was experiencing.
I've been running the same task that would normally panic the system within 30
min for almost 24 hours now and not a single panic and still running strong.
Thanks a million!
Michael
> On Feb 20, 2017, at 10:46
I can poke around to find one or recreate.
thx
Linda
On 2/21/17 10:04 AM, Dale Ghent wrote:
This is not normal. Do you have a crash dump available, or at least a panic
string?
/dale
On Feb 21, 2017, at 10:57 AM, Linda Kateley wrote:
Has anyone run into omnios
Has anyone run into omnios panicing in virtualbox?
I have been working on a video series of napp-it and when I put them all
together(omni and napp-it) on my big mac(running el cap) I get a day or
2 in, and panic. I seem to be able to run it on 16 or 18 without updates
easily but when I run