From owner-freebsd-current Tue May 4 21: 6:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 7C77C1528C for ; Tue, 4 May 1999 21:06:09 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id VAA50386; Tue, 4 May 1999 21:05:57 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372FC3B0.A0587884@MexComUSA.net> Date: Tue, 04 May 1999 21:06:08 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Stefan Bethke Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: netatalk (atalkd,papd,afpd) References: <26309987.3134862184@monster.transit-a.hanse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Bethke wrote: > Edwin Culp wrote: > > > I just realized that I have lost netatalk (atalkd/papd/afpd) seems to > > have silently died within the last week or so, for no clear reason. Has > > anyone else, who is running current and netatalk, seen this? (Misery > > loves company:-) I'm going to start looking for a problem. > > I've just compiled and installed netatalk-asun, and everything seems fine > on my -current from about two day ago... > > I'll try with netatalk sometime soon. > > Stefan > Good news, maybe it's fixed. I'll give it another try. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message