From owner-freebsd-questions Tue Oct 24 21:10:58 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.monochrome.org (monochrome.org [206.64.112.124]) by hub.freebsd.org (Postfix) with ESMTP id 5D83D37B479 for ; Tue, 24 Oct 2000 21:10:56 -0700 (PDT) Received: from localhost (faro [192.168.1.7]) by mail.monochrome.org (8.9.3/8.9.3) with SMTP id AAA33439 for ; Wed, 25 Oct 2000 00:10:55 -0400 (EDT) (envelope-from chris@monochrome.org) Date: Wed, 25 Oct 2000 00:10:55 -0400 (EDT) From: Chris Hill X-Sender: chris@localhost To: FreeBSD Questions List Subject: Netatalk stopped working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running netatalk 1.4b2 (from the ports) under 3.3R, and have been using this combination for about a year on this machine. It's worked fine ever since 3.3R came out last October. This past weekend I was playing around with my (seemingly unrelated) firewall configuration on the same machine, which involved multiple "shutdown"s to single-user mode, followed by exiting to multi-user. At some point during this iterative process, I noticed that netatalk was not coming back up like it used to. On boot, I'd get messages to the effect of "AppleTalk not up! Child exited with 1" and "Can't register :". When I run the shell script /usr/local/etc/rc.d/netatalk.sh manually as root, I get no error message but the daemons don't start. Yes, I'm waiting long enough. I haven't touched the startup script or the config file, and this machine is not trying to grab the same node number as my other netatalk server. My ethernet card is still multicast capable and still properly configured, just as it has been since 1998. Any ideas what might be causing this? Could ipfw be blocking the port(s) all of a sudden, when it never has before? Many thanks in advance. -- Chris Hill chris@monochrome.org [1] Bus error netscape To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message