https://access.redhat.com/solutions/36223
SOLUTION 已验证 - 已更新 2014年三月4日18:26 -
环境
- Red Hat Enterprise Linux 6
- NetworkManager
问题
-
Network Manager gets started, but before the ethernet interfaces can get IP addresses, services that rely on a network connection are started. Problem seen with LDAP and autofs which relies on LDAP for the maps, so nothing gets automounted.
-
What's the equivalent NETWORKDELAY in RHEL 6
决议
- Add "NETWORKWAIT=yes" to
/etc/sysconfig/networkto block until the interfaces have addresses for NetworkManager.
根源
As per /etc/init.d/NetworkManager
if [ -n "${NETWORKWAIT}" ]; then
[ -z "${LINKDELAY}" ] && LINKDELAY=10
echo -n $"Waiting for network..."
nm-online -q --timeout=$LINKDELAY || nm-online -q -x --timeout=30
[ "$?" = "0" ] && success "network startup" || failure "network startup"
echo
[ -n "${NETWORKDELAY}" ] && /bin/sleep ${NETWORKDELAY}
fi
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/$servicename
}
本文介绍了解决Red Hat Enterprise Linux 6中NetworkManager启动过快导致网络依赖服务如LDAP和autofs无法正常工作的问题。通过在/etc/sysconfig/network中添加NETWORKWAIT=yes配置,可以确保在所有接口获取到IP地址后再启动这些服务。

被折叠的 条评论
为什么被折叠?



