[Bug 225804] New: ypbind and autofs doesn't work automatically
https://bugzilla.novell.com/show_bug.cgi?id=225804 Summary: ypbind and autofs doesn't work automatically Product: openSUSE 10.2 Version: RC 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: kukuk@novell.com ReportedBy: dkukawka@novell.com QAContact: qa@suse.de This is a bug we have since sled10, openSUSE 10.1 and now again on 10.2. I configured veryting in Yast to use ypbind and to start automatically (with NIS) the automounter, but this never work togehter with Networkmanager. After each boot I have to call rcypbind and rcautofs restart. This never work automatically. Sometimes it help (depends on the machine) to change NM_ONLINE_TIMEOUT e.g. from 0 to 15. We need a solution which always work as before 10.1 or with ifup. If I understand the problem correct there is should be a bug in ypbind. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225804 kukuk@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dkukawka@novell.com ------- Comment #1 from kukuk@novell.com 2006-12-05 02:15 MST ------- Your report is missing all details what your doing, if ypbind is started or not, etc. So useless. ypbind listens to NetworkManager and goes online, if NetworkManager has a working connection. autofs cannot do that, so it has to be started much later by NetworkManager, or you will have a race and autofs cannot find the entries. But the informations in this report are useless. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225804 ------- Comment #2 from kukuk@novell.com 2006-12-05 02:16 MST ------- "If I understand the problem correct there is should be a bug in ypbind." This is without any informatins pure, useless FUD. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225804 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thoenig@novell.com Status|NEEDINFO |ASSIGNED Info Provider|dkukawka@novell.com | ------- Comment #4 from dkukawka@novell.com 2006-12-05 04:55 MST ------- If I don't use a timeout (NM_ONLINE_TIMEOUT=0): - ypbind and autofs get skipped while boot (ypbind: no domainname set ...) - after finished boot, I get a IP address, but ypbind and autofs are not running ... mean: no login, no autofs What is different between normal boot and this case (which work): - rcnetwork stop - rcypbind start (.... no NIS server found ..., but ypbind is running and not skipped) - rcnetwork start - rcautofs (re)start IMO ypbind should not skip while boot if there is no domainname, it should run in background until NM run complete. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225804 kukuk@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #5 from kukuk@novell.com 2006-12-12 07:53 MST ------- It seems some Network background is necessary: the domainname is not supposed to be changed in a running system. No application does ever reread the domainname after it is started. So what you are wish to do is not compatible with how it works and cannot be fixed. That's why it was always and will ever be a bad idea to use NIS in conjunction with NetworkManager and dhcp. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com