From owner-freebsd-questions Mon May 14 10:27:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id BECE737B422 for ; Mon, 14 May 2001 10:27:44 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (Sturm@klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.11.3/8.11.3) with ESMTP id f4EHRiL72997 for ; Mon, 14 May 2001 19:27:44 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Mon, 14 May 2001 19:27:44 +0200 (CEST) From: "Hartmann, O." To: Subject: How to obtain a path-variable to an subsystem? (fwd) 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 Dear Sirs. Well, this question is maybe not of concern of this group. I use magicfilter for driving our printer servers and before changing the installation (changed hardware and set up a new FBSD) all things worked fine to us. I can not print any job because magicfilter uses a2ps and a2ps uses as many other tools for themselfes other tools which they call. Now I get a lot of error messages in the log for each printer that fixps and related could not be loaded, but fixps is available! It seems to me to be a problem how to pass the environment variables to the subsystem of printers and force them to search at special locations like //usr/local/bin. Does anyone know how to perform this? -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message