My apologies if this appears twice. I am apparently having sendmail problems too. My system (upgraded this week from 9.1 to 9.2) has suddenly started acting strange about bringing up my eth0 interface. It uses the 3c59x driver. I noticed that after a complete boot into runlevel 5, the eth0 interface has no ip address. If I then run "rcnetwork restart", it brings up the interface properly with the correct IP and netmask. I rebooted into runlevel 2 in order to simplify things, and I can see the network script say that eth0 has ip address 192.168.0.2 with appropriate netmask. But at the end of the boot into runlevel 2, if I check with ifconfig, eth0 now has no ip address. I tried rebooting and going into single user mode and then manually running each of the scripts (in order) in /etc/rc.d/rc2.d. The network script again brings up eth0 with the correct IP and netmask, and at the end of running all the scripts the network is properly configured and running fine. Even after that, I can "init s" and then "init 2", and at the end of init 2 the interface will now be properly brought up. Once it have brought it up with rcnetwork restart I can bring it up and down at will, and it will come up and down properly even when changing runlevels. So I am kind of flummoxed as to why it doesn't finish a normal boot into level 2 or 3 or 5 with the interface having the proper IP and netmask, but it will be OK if I run "rcnetwork restart". Here is an excerpt from the /var/log/boot.msg file: Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30) eth0 configuration: eth-id-00:50:da:25:86:46 eth0 IP address: 192.168.0.2/24 doneSetting up service network . . . . . . . . . . . . . . . .done <notice>exit status of (network) is (0) Nothing in the boot.msg file or /var/log/messages shows anything after that regarding eth0 losing its configuration. Any ideas, please? Thank you Michael -- San Francisco, CA