Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Sep 2005 15:18:52 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        dick hoogendijk <dick@nagual.st>
Cc:        fbsdq <questions@freebsd.org>
Subject:   Re: Xprt
Message-ID:  <20050920191852.GA10289@xor.obsecurity.org>
In-Reply-To: <20050920211817.28f3b36e.dick@nagual.st>
References:  <20050920201411.2914a331.dick@nagual.st> <44u0gfsh3j.fsf@be-well.ilk.org> <20050920211817.28f3b36e.dick@nagual.st>

next in thread | previous in thread | raw e-mail | index | archive | help

--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 20, 2005 at 09:18:17PM +0200, dick hoogendijk wrote:
> On 20 Sep 2005 14:56:48 -0400
> Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote:
>=20
> > dick hoogendijk <dick@nagual.st> writes:
> >=20
> > > Yesterday I upgraded my xorg-printserver. Afterwards my Xprt would
> > > not start. Looking at /usr/X11R6/etc/rc.d/xprint.sh I did not have a
> > > POSIX-shell. <???> Hmmm.. seems you need ksh or bash for xprint all
> > > of a sudden. A warning would have been nice.
> >=20
> > That script only requires a POSIX shell, and our standard /bin/sh
> > should work fine.  I just tried it, and it does work for me.
>=20
> That's what I expected. But if you look into the script you'll
> see#!/bin/sh
>=20
> #########################################################################=
###
>=20
> # Force use of a POSIX conformant sh=20
> [ "$1" !=3D "posix_sh_forced" -a -x /bin/ksh  ]            &&
> exec /bin/ksh  "$0" posix_sh_forced "$@" [ "$1" !=3D "posix_sh_forced" -a
> -x /bin/bash ]            && exec /bin/bash --norc --noprofile "$0"
> posix_sh_forced "$@" [ "$1" !=3D "posix_sh_forced" -a
> -x /usr/local/bin/ksh ]   && exec /usr/local/bin/ksh "$0"
> posix_sh_forced "$@" [ "$1" !=3D "posix_sh_forced" -a
> -x /usr/local/bin/bash ]  && exec /usr/local/bin/bash --norc
> --noprofile "$0" posix_sh_forced "$@" if [ "$1" !=3D
> "posix_sh_forced" ] ; then echo "${0}: ## FATAL ERROR: No POSIX-shell
> found."  1>&2 exit 1 fi
> #######################################
>=20
> As you can see, /bin/sh is NOT mentioned (and thus 'not found')
> Only ksh and bash seem to be supported. Strange..
> Sure I can alter the startup script, but I'm not supposed to do this,
> am I?

Talk to the maintainer.

Kris

--pWyiEgJYm5f9v55/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDMGCbWry0BWjoQKURAjhyAJ42/tSrNbQZY9mLNoGSNuIBHiooHwCg/Nu/
9a0w3n8G6PyG9plXwQ1meq4=
=ak5v
-----END PGP SIGNATURE-----

--pWyiEgJYm5f9v55/--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050920191852.GA10289>