On Mon, Jul 16, 2007 at 11:49:51PM +0200, Elimar Riesebieter wrote: > Please find attached bootlog.-
Thanks, but this doesn't make any sense! :-) > Mon Jul 16 23:44:01 2007: Setting up networking.... > Mon Jul 16 23:44:01 2007: Configuring network interfaces...Internet Systems > Consortium DHCP Client V3.1.0rc2 > Mon Jul 16 23:44:01 2007: Copyright 2004-2007 Internet Systems Consortium. > Mon Jul 16 23:44:01 2007: All rights reserved. > Mon Jul 16 23:44:01 2007: For info, please visit http://www.isc.org/sw/dhcp/ > Mon Jul 16 23:44:01 2007: > Mon Jul 16 23:44:02 2007: Listening on LPF/eth0/00:0a:5e:5f:b5:b4 > Mon Jul 16 23:44:02 2007: Sending on LPF/eth0/00:0a:5e:5f:b5:b4 > Mon Jul 16 23:44:02 2007: Sending on Socket/fallback > Mon Jul 16 23:44:02 2007: option_space_encapsulate: option space agent does > not exist, but is configured. > Mon Jul 16 23:44:02 2007: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 8 > Mon Jul 16 23:44:02 2007: DHCPOFFER from 192.168.200.1 > Mon Jul 16 23:44:02 2007: option_space_encapsulate: option space agent does > not exist, but is configured. > Mon Jul 16 23:44:02 2007: DHCPREQUEST on eth0 to 255.255.255.255 port 67 > Mon Jul 16 23:44:02 2007: DHCPACK from 192.168.200.1 > Mon Jul 16 23:44:02 2007: bound to 192.168.200.202 -- renewal in 13715 > seconds. This is S40networking. > Mon Jul 16 23:44:03 2007: Starting portmap daemon.... This should be S43portmap. It's normal that it doesn't print anything on success. > Mon Jul 16 23:44:04 2007: mount.nfs: rpc.statd is not running but is required > for remote locking > Mon Jul 16 23:44:04 2007: Either use "-o nolocks" to keep locks local, or > start statd. > Mon Jul 16 23:44:04 2007: mount.nfs: rpc.statd is not running but is required > for remote locking > Mon Jul 16 23:44:04 2007: Either use "-o nolocks" to keep locks local, or > start statd. > Mon Jul 16 23:44:04 2007: mount.nfs: rpc.statd is not running but is required > for remote locking > Mon Jul 16 23:44:04 2007: Either use "-o nolocks" to keep locks local, or > start statd. > Mon Jul 16 23:44:04 2007: mount.nfs: rpc.statd is not running but is required > for remote locking > Mon Jul 16 23:44:04 2007: Either use "-o nolocks" to keep locks local, or > start statd. > Mon Jul 16 23:44:04 2007: mount.nfs: rpc.statd is not running but is required > for remote locking > Mon Jul 16 23:44:04 2007: Either use "-o nolocks" to keep locks local, or > start statd. > Mon Jul 16 23:44:04 2007: mount.nfs: rpc.statd is not running but is required > for remote locking > Mon Jul 16 23:44:04 2007: Either use "-o nolocks" to keep locks local, or > start statd. > Mon Jul 16 23:44:04 2007: done. But this is S45mountnfs.sh! Why didn't S44nfs-common start? > Mon Jul 16 23:44:04 2007: Starting portmap daemon...Already running.. And here S43portmap is again! > Mon Jul 16 23:44:04 2007: Starting NFS common utilities: statd idmapd. ...and finally S44nfs-common. > Mon Jul 16 23:44:06 2007: Setting sensors limits: done. This is S47lm-sensors. Now for some reason S45mountnfs is not run. So, It seems like after S40networking, something goes really awry and out-of-turn, before continuing with the usual start-up sequence. Perhaps it's trying to mount after ifup eth0 -- have you set it to do that somehow? I see there's something about ASYCNMOUNTNFS in /etc/network/if-up.d/mountnfs, but I cannot find where it's supposed to be set. In /etc/default/rcS perhaps; could you check there? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
