http://defect.opensolaris.org/bz/show_bug.cgi?id=8924
Summary: Automatic location doesn't seem as functional when used
with User NCP
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: NEW
Status Whiteboard: nwam1-build:2009-05-12
Severity: normal
Priority: P3
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: dkenny at opensolaris.org
QAContact: nwam-dev at opensolaris.org
I don't know if it's just co-incidence, but after an upgrade, the location name
nameservices doesn't seem to get correctly configured.
In this case, as expected, the User NCP is selected as the default NCP, and the
Automatic Location is active. But it doesn't seem to matter if I refresh nwam
or the location, it doesn't seem to fill everything out correctly, sometimes
it's the resolv.conf and other's the nsswitch.conf is still files instead of
DNS.
Yet when I switch to the Automatic NCP, the location things seem to start
working again. Is there some difference in the operation of the Automatic
location depending on the selected NCP? It would appear so.
Is there any useful debugging or logs I can pick up that would be useful to
debugging the location?
--
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.
