Michael Hunter wrote:
> On Wed, 25 Apr 2007 17:41:50 -0400
> Sebastien Roy <Sebastien.Roy at Sun.COM> wrote:
> 
> [...]
>> Is this a known bug?  I can file one if it isn't.
> 
> Can you enable nwamd/debug on svc:/network/physical:nwam and make sure
> you are capturing syslog debug, notice, info, and warning severities
> for the daemon facility if you get a chance.  We should be able to tell
> you what is going wrong from our end.

Nice of you to offer. :-)  I've enabled nwamd/debug, and the strange 
part is that nwamd logs nothing at boot.  It's only after I've done the 
svcadm restart nwam that I get debug log messages:

bash-3.00# svcprop -p nwamd/debug nwam
true
bash-3.00# grep daemon\.debug /etc/syslog.conf
daemon.debug                                    /var/adm/daemon.log
bash-3.00# ps -ef | grep nwamd
     root 100028      1   0 21:11:42 ?           0:00 /lib/inet/nwamd
     root 100419 100296   0 21:17:18 console     0:00 grep nwamd
bash-3.00# cat /var/adm/daemon.log
<nothing!>
bash-3.00# svcadm restart nwam
bash-3.00# cat /var/adm/daemon.log
Apr 25 18:19:49 unknown nwamd[100026]: [ID 781624 daemon.info] nwamd pid 
100026 started
Apr 25 18:19:49 unknown nwamd[100026]: [ID 740153 daemon.debug] 1: 
lookup_count_property(nwamd, scan_interval) returns 120
Apr 25 18:19:49 unknown nwamd[100026]: [ID 740153 daemon.debug] 1: Read 
daemon configuration properties.
Apr 25 18:19:49 unknown nwamd[100026]: [ID 740153 daemon.debug] 1: 
started with privs all
Apr 25 18:19:49 unknown nwamd[100028]: [ID 740153 daemon.debug] 1: 
signal handler thread: 2
Apr 25 18:19:49 unknown nwamd[100028]: [ID 740153 daemon.debug] 1: 
initialize_interfaces: setting link_layer_profile(0) to NULL
<...>

At that point, IP addresses are properly configured via DHCP.

-Seb

Reply via email to