Network starting too late for fstab CIFS mounts

[Clyde E. Kunkel]

Clyde E. Kunkel wrote:
> Tail of dmesg shows that upstart is attempting to mount fstab entries 
> before network is up.  This results in failure.  Is there something I 
> can adjust in upstart?
> 
> Bugzilla Bug 439242: fstab network mounts fail due to late network startup
> 
> dmesg snippet:
> <snip>
> IA-32 Microcode Update Driver: v1.14a 
> ip6_tables: (C) 2000-2006 Netfilter Core Team
> nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> ip_tables: (C) 2000-2006 Netfilter Core Team
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
>  CIFS VFS: Error connecting to IPv4 socket. Aborting operation
>  CIFS VFS: cifs_mount failed w/return code = -101
> Bluetooth: Core ver 2.11
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: L2CAP ver 2.9
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
> Bluetooth: RFCOMM ver 1.8
> sky2 eth0: enabling interface
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> eth0: no IPv6 routers present
> <snip>
> 
> Is there something I can adjust in upstart?

Ughhh...sorry didn't see the e-mail address in the dmesg 
snippet..deleting in this reply

-- 
---------------------------------
Regards,

Old Fart