Date: 12 Nov 2004 08:47:14 +0100 From: Christian Laursen <xi@borderworlds.dk> To: Greg Lewis <glewis@eyesbeyond.com> Cc: freebsd-java@freebsd.org Subject: Re: The new javavmwrapper and PATH Message-ID: <86sm7fqzjx.fsf@borg.borderworlds.dk> In-Reply-To: <20041112040220.GA76106@misty.eyesbeyond.com> References: <86ekj0c79e.fsf@borg.borderworlds.dk> <20041112040220.GA76106@misty.eyesbeyond.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lewis <glewis@eyesbeyond.com> writes: > On Fri, Nov 12, 2004 at 12:09:49AM +0100, Christian Laursen wrote: > > I just upgraded to the new javavmwrapper and noticed that one of my java > > programs stopped working. > > > > It runs binaries usually in the path but javavmwrapper sets the path to > > "/bin:/sbin:/usr/bin:/usr/sbin". > > > > Shouldn't $LOCALBASE/bin and $LOCALBASE/sbin be part of the path as well? > > > > Or would it perhaps be better to set the original path back before starting > > the chosen java binary? > > Does the attached diff fix this for you? Yes, thank you. -- Christian Laursen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86sm7fqzjx.fsf>