From owner-freebsd-current Sun Jan 31 16:21:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19272 for freebsd-current-outgoing; Sun, 31 Jan 1999 16:21:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19267 for ; Sun, 31 Jan 1999 16:21:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id QAA79810; Sun, 31 Jan 1999 16:21:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Paul cc: current@FreeBSD.ORG, obrien@nuxi.com Subject: Re: Even more interesting NFS problems.. In-reply-to: Your message of "Sun, 31 Jan 1999 12:14:32 EST." <199901311714.MAA01425@skynet.ctr.columbia.edu> Date: Sun, 31 Jan 1999 16:21:41 -0800 Message-ID: <79808.917828501@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Err.... On all of the machines where I use amd, I don't use -l syslog. > I use -l /tmp/.automsg (or some other filename that lusers aren't likely You're right, that does produce more information. Unfortunatly, not enough to help diagnose the problem. :( I think something more fundamental is broken here since it doesn't even log the requests you make of it. All you get are the startup messages, then silence forever more. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message