* Ravindra Jaju ([EMAIL PROTECTED]) wrote :
> On Wed, Jul 10, 2002 at 07:49:25AM -0700, Joshua Slive wrote:
> > On Wed, 10 Jul 2002 [EMAIL PROTECTED] wrote:
> > > In apache 1.3 we had this little trick:
> > >
> > > if [ "x`$aux/getuid.sh`" != "x0" -a "x$port" = "x" ]; then
> > > conf_port="8080"
> > > fi
> > >
> > > to make the port 8080 when the user is not root - thus to reduce the
> > > number of 'apache wont start' newby errors and be generally convenient for
> > > the masses (and disorganized people like me).
> > >
> > > Has that been dropped from 2.0 for a reason or by accident ?
> >
> > In my opinion, that was never a good idea. The newbie users are simply
> > confused by this, because they have a server which starts up but can't be
> > accessed at http://localhost/. And people who do very sensible things
> > like build/install as non-root and then startup as root must go through an
> > extra step to fix this change.
>
> How about an extra echo:
>
> if [ "x`$aux/getuid.sh`" != "x0" -a "x$port" = "x" ]; then
> conf_port="8080"
> echo "Non-root process. Server will run on port $conf_port"
> fi
I think the best solution is to educate the user, rather than to do
something unexpected.
if [ "x`$aux/getuid.sh`" != "x0" -a "x$port" = "x" ]; then
echo "You are not currently the superuser. Therefore we can't start
apache listening on a privileged port (One above 1024)"
fi
(Line wrapped by mail client, obv this snippet would break)
This also (I guess) presupposes that the admin is trying to start a server
on a priv port. If they're not, then they're gonna be even more pissed if we
change unpriv ports at random on them.
Cheers,
-Thom
--
Thom May -> [EMAIL PROTECTED]
Step forward MP3.com founder Michael Robertson, a man with a talent for
soundbites: "All I know is that I'm being sued for unfair business
practices by Microsoft. Hello pot? It's kettle on line two," he told Reuters.
