Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Date: Fri, 30 Aug 2002 12:45:25 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <46B1BBD1961A564E9BE4B97238B3EF0C10C8C1@exchangeserver>
content-class: urn:content-classes:message
Thread-Topic: [users@httpd] Apache for user account
Thread-Index: AcJPzx38vetEor0ETMuDFbZERpdtIwAABJ2w
From: "Andrew Kenna" <andrewk@stamina.com.au>
To: <users@httpd.apache.org>
Subject: RE: [users@httpd] Apache for user account

change the path that it writs to be =
/path/to/$ENV{'USERNAME'}'/home/directory in the apachectl


Andrew


-----Original Message-----
From: manav [mailto:manav@glue.umd.edu]
Sent: Friday, 30 August 2002 12:42 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Apache for user account


well the diff httpd.conf and different port works well for the most =
part,
just that the httpd script somehow writes a pid file in /var/lock and =
that
sorta overlaps, how do I get it to write it to users home dir?
I changed the httpd.conf file but it still writes in the /var/lock =
directory

:-(

----- Original Message -----
From: "John K. Sterling" <john@sterls.com>
To: <users@httpd.apache.org>
Sent: Thursday, August 29, 2002 9:35 PM
Subject: Re: [users@httpd] Apache for user account


> On Thursday, August 29, 2002, at 07:53 PM, Chris Taylor wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Well, if it's an "intranet" type thing.......hmmm.
> >
> > I would consider using one Apache thing with an Alias for everyone's
> > webroot. This way you run one Apache and get in via:
> >
> > http://www.example.com/jane/ etc. Obviously far easier to update
> > Apache etc. There are (many) other solutions. If you have a lot of
> > users (>50 or so?) then writing an Alias for each one would be
> > undesirable, but I'm sure someone here could suggest something
> > similar.
> >
>
> hmm, i don't know if that is good advice in this situation.  If you
> want each user to truly have their own webserver that they can stop =
and
> start, then the different port solution is probably best.  This would
> usually apply to users that are developers or have specific config
> information that they would want to control.  If, however, these users
> are just displaying static content or cgis (and don't need special
> configuration for their server) then mod_userdir would probably help
> you out (and no aliasing needed).
>
> sterling
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server =
Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server =
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org