Date: Thu, 9 Dec 1999 09:48:48 +0100
From: Martin Kraemer <martin@pgtm0035.mch.sni.de>
To: new-httpd@apache.org
Subject: Re: [PATCH]Apache 1.3.9 Port to OS/390 Unix System Services -- The
 Basics -- cleaned up
Message-ID: <19991209094848.A11728@pgtm0035.mch.sni.de>
References: <384EB8FC.8598C75C@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <384EB8FC.8598C75C@us.ibm.com>;
 from oviesb@us.ibm.com on Wed, Dec 08, 1999 at 12:01:00PM -0800
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org
Status: O

On Wed, Dec 08, 1999 at 12:01:00PM -0800, Ovies Brabson wrote:
> > I was dreaming of something along the line of...
> > > +        --server-uid=*)
> > > +            conf_user="$apc_optarg"
> > > +            # protect the '#' against interpretation as comment
> > > +            case x"${conf_user}" in
> > > +              "#"*)  conf_user="\\\\${conf_user}";;
> > > +              "\\#"*)conf_user="\\${conf_user}";;
> > > +            esac
> > > +            ;;
> > ...and dito for conf_group.
> >
> OK.  Changed it.  Why is this not a problem for some of the other args
> passed to configure?

Because none of the other arguments possibly start with (or contain)
a '#' char (which is interpreted the beginning of a comment in one
of the later string assignments). Each assignment cuts half the number of
the '\' escape chars, so if you if you start out with
    configure --server-gid="#4711"
and finally do NOT end up with

    conf_group       = \#4711
    ...
		 cat $(TOP)/conf/$${conf}-dist ) |\
		 sed -e '/# LoadModule/r $(TOP)/$(SRC)/.apaci.install.conf' \
			...
			-e 's;Group #-1;Group $(conf_group);' \
			...
			> $(TOP)/$(SRC)/.apaci.install.tmp && \

in the generated Makefile, then the resulting configuration file will
be broken.

    Martin
-- 
<Martin.Kraemer@MchP.Siemens.De>             |    Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-41143 | 81730  Munich,  Germany