From owner-freebsd-java@FreeBSD.ORG Sat Dec 17 13:39:29 2005 Return-Path: X-Original-To: freebsd-java@hub.freebsd.org Delivered-To: freebsd-java@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CCE216A41F; Sat, 17 Dec 2005 13:39:29 +0000 (GMT) (envelope-from lawrance@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 496B143D45; Sat, 17 Dec 2005 13:39:29 +0000 (GMT) (envelope-from lawrance@FreeBSD.org) Received: from freefall.freebsd.org (lawrance@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBHDdT9R050887; Sat, 17 Dec 2005 13:39:29 GMT (envelope-from lawrance@freefall.freebsd.org) Received: (from lawrance@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBHDdSQJ050883; Sat, 17 Dec 2005 13:39:28 GMT (envelope-from lawrance) Date: Sat, 17 Dec 2005 13:39:28 GMT From: Sam Lawrance Message-Id: <200512171339.jBHDdSQJ050883@freefall.freebsd.org> To: leafy@leafy.idv.tw, lawrance@FreeBSD.org, freebsd-java@FreeBSD.org Cc: Subject: Re: ports/74760: java/javavmwrapper messes up amavisd-new X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 13:39:29 -0000 Synopsis: java/javavmwrapper messes up amavisd-new State-Changed-From-To: open->closed State-Changed-By: lawrance State-Changed-When: Sat Dec 17 13:23:05 UTC 2005 State-Changed-Why: I can't reproduce this on an updated 6.x system. I suspect something local to your system is causing this problem. I do not think this problem is specifically related to java. The error message given is actually a result of amavisd-new attempting to run and use the "file" utility. Somehow, yours is running java as a result. Check to make sure that your file(1) utility is in place and working correctly. Check for any other executables named "file" in your $PATH that might be interfering with normal operation. Otherwise, I can only suggest hacking up your amavisd file to try to get a better idea of what is going on. Closed without action. http://www.freebsd.org/cgi/query-pr.cgi?pr=74760