Re: Mysql -> Postgresql pitfalls - Mailing list pgsql-docs

From Chad N. Tindel
Subject Re: Mysql -> Postgresql pitfalls
Date
Msg-id 20030802170410.GA12300@calma.pair.com
Whole thread Raw
In response to Re: Mysql -> Postgresql pitfalls  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Mysql -> Postgresql pitfalls
Re: Mysql -> Postgresql pitfalls
Re: Mysql -> Postgresql pitfalls
List pgsql-docs
> > <RANT>As a programmer, I personally would never write code that kept
> > people from running things as root.  I mean, what is the point?
>
> If someone roots your box, it's not our fault.  Simple as that.

I didn't say "require them to run as a non-root user".  I said "Give them
the choice to decide what is correct for their environment".  In the case
of apache, there are many internal webservers that are not exposed to the
threat of the public internet; for such servers, it may be appropriate to run
apache as root because it simplifies the administration and automation of
tasks.  But to do so, one has to know how to re-compile apache, which will
exclude a lot of your basic garden variety administrators.  Its very
un-friendly programming.

Chad

pgsql-docs by date:

Previous
From: Roberto Mello
Date:
Subject: Re: Mysql -> Postgresql pitfalls
Next
From: "Chad N. Tindel"
Date:
Subject: Re: Mysql -> Postgresql pitfalls