After an upgrade of samba-common and samba-client from 3.0.22 to 3.0.23 my linux machine was not able to boot if it connected to a windows network. The boot process stops when hal is being started, blocking each activity. However, if the computer is not connected to a network, or to a linux-only network, everythings works fine. A workaround to boot was boot with unplugged network upon completion: /sbin/init 1 connect network /sbin/init 5 In addition the avahi-daemon receives a timeout. After downgrading to 3.0.22 I discoverd no problems. System: fc 5 kernel-2.6.17-1.2157_FC5 on a thinkpad t40
The bahaviour is the same with 3.0.23a Here are some log snippets (unfortunately they are in German) From /var/log/samba/log.wb-<computername>: [2006/07/31 09:13:41, 0] lib/util_sock.c:write_data(564) write_data: write failure. Error = Datenübergabe unterbrochen (broken pipe) [2006/07/31 09:13:41, 0] nsswitch/winbindd_dual.c:fork_domain_child(825) Could not write result [2006/07/31 09:15:40, 1] nsswitch/winbindd_misc.c:winbindd_dual_getdcname(202) Can't contact the NETLOGON pipe From /var/log/winbind.log: [2006/07/31 09:11:05, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23a-1.fc5.1 started. Copyright The Samba Team 2000-2004 [2006/07/31 09:15:39, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23a-1.fc5.1 started. Copyright The Samba Team 2000-2004
Dirk, Are you sure this is not an SeLinux thing?
probably no samba bug and no feedback from submitter. closing.