Ticket #31 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

fix of failures of init scripts

Reported by: sbrabec@… Owned by: lennart
Milestone: Avahi 0.6.10 Component: avahi-daemon
Keywords: Cc:

Description

In SuSE Linux 10.1 I have experienced failures of avahi-dnsconfd init script.

Apr  5 19:27:15 linux avahi-dnsconfd[3390]: connect(): No such file or directory
Apr  5 19:27:15 linux avahi-dnsconfd[3390]: Failed to connect to the daemon. This probably means that you
Apr  5 19:27:15 linux avahi-dnsconfd[3390]: didn't start avahi-daemon before avahi-dnsconfd.

It seems to be related to asynchronous starting of scripts - avahi-dnsconfd is started before finishing of initialization of avahi-daemon.

There is a quick hack, which seems to fix it. Other possible fixes are:

- Change avahi-daemon to not detach so early.

- Change avahi-dnsconfs to not give up so early and retry.

The fix is for SuSE Linux, but it may affect other platforms, too.

--- initscript/suse/avahi-daemon.in
+++ initscript/suse/avahi-daemon.in
@@ -17,6 +17,15 @@
     start)
         echo -n "Starting Avahi daemon"
         /sbin/startproc $AVAHI_BIN -D
+	rc_check
+	for (( n=0 ; n<10 ; n++ )) ; do
+	    if test -f /var/run/avahi-daemon/pid ; then
+		break
+	    else
+		echo -n "."
+		sleep 1
+	    fi
+	done
 	rc_status -v
         ;;
     stop)

Reference:  https://bugzilla.novell.com/show_bug.cgi?id=150902

Change History

Changed 7 years ago by anonymous

  • milestone set to Avahi 0.6.10

Changed 7 years ago by sebest

  • status changed from new to closed
  • resolution set to fixed

thanx, commited

Note: See TracTickets for help on using tickets.