Uwe Dippel writes: > [iWhich builds exactly?][/i] > > All, since rum was in Nevada. In any case, including 108.
OK; that rules out a number of things. > # dmesg | grep rum > Feb 23 23:30:14 solu mac: [ID 744254 kern.info] NOTICE: rum1 link up > Feb 23 23:32:06 solu mac: [ID 486395 kern.info] NOTICE: rum1 link down > Feb 23 23:32:46 solu mac: [ID 744254 kern.info] NOTICE: rum1 link up That doesn't look too happy. Is the driver just reporting link up and down repeatedly over time? If so, then that might be the cause. > [i]It's possible to run dhcpagent (the DHCP client) in a debug mode that > will print a _large_ amount of data to the system log file. To do > this, set up syslogd to log daemon.debug to a file[/i] > > How to do this, any hint? # /bin/echo "daemon.debug\t/var/adm/debug" >> /etc/syslog.conf # touch /var/adm/debug # pkill -HUP syslogd (Yes, the "touch" is important. Syslogd doesn't create its own files. See syslogd(1M) and syslog.conf(4) for more information.) -- James Carlson, Solaris Networking <[email protected]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
