For those outside of the development group using and/or testing this you might 
want to hold off using tonights build until we've figured out what is wrong.  
OTOH It is possible that the problem is unique to my setup so if you have spare 
patience and time go ahead and give it a try.

                               mph

----- Original Message -----
From: [email protected]
Date: Thursday, April 23, 2009 3:36 pm
Subject: [nwam-dev] [Bug 8390] New: 'svcadm disable nwam' send nwam into 
maintenance
To: nwam-dev at opensolaris.org


> http://defect.opensolaris.org/bz/show_bug.cgi?id=8390
> 
>            Summary: 'svcadm disable nwam' send nwam into maintenance
>     Classification: Development
>            Product: nwam
>            Version: unspecified
>           Platform: ANY/Generic
>         OS/Version: All
>             Status: NEW
>           Severity: minor
>           Priority: P2
>          Component: ON daemon
>         AssignedTo: nwam-dev at opensolaris.org
>         ReportedBy: michael.hunter at sun.com
>          QAContact: nwam-dev at opensolaris.org
> 
> 
> Created an attachment (id=1797)
>  --> (http://defect.opensolaris.org/bz/attachment.cgi?id=1797)
> made with gcore when nwamd is hung
> 
> After the locking change putback I see a hang when nwamd is disabled.  
> Even
> though that was expected I've created this bug to track it.  Attached 
> is a core
> of nwamd made after the disable but before nwam goes into maintenance. 
>  From
> the stack you can clearly see the thread deadlocked.
> 
> -- 
> Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the QA contact for the bug.
> You are the assignee for the bug.
> _______________________________________________
> nwam-dev mailing list
> nwam-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/nwam-dev

Reply via email to