[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lenny rant


I use a system where this is done. The admin chose to create separate
config files, ie copy the apache2.conf file. Then he wrote some init.d
scripts to run these apache2 instances using something like:

apache2 -f /etc/apache2/other.conf

This file in turn included files specific to its configuration.

A nice thing about apache2 is that everything is modular, so you can
have certain configurations load modules (ie the LoadModule directive)
while other configurations do not. Then you can have the same Apache
httpd install providing different services based on the config file.

And you can still apt-get update it.

I noticed some people on the list were being a bit... rude, perhaps,
in their response, but I think they raise a valid point... It's
important to keep software up to date if possible, especially when
Apache1 is no longer actively maintained (even if serious bug fixes
are applied). Apache2 is pretty awesome stuff, and in tradition with
their development process, it's been pretty secure/stable throughout.
I'm glad you're taking their suggestions to heart, namely, installing
Apache2 instead of trying to keep Apache1 installed indefinitely.

Hope this helps & best of luck.



On Sun, Apr 12, 2009 at 11:12 AM, Michael Moritz <mimo@gn.apc.org> wrote:
> Well thanks for all the answers - though some were a bit personal: being
> called incompetent and lazy is not what i expected. i guess in general people
> complain about software not being updated quickly enough rather than not being
> old enough.
> one last question - does anyone have a suggestion on how to run two separate
> instances of apache2 under different users and keep upgrading simple?
> thanks
> mimo
> ps.: apologies for posting in html before - must be a new default in kde4
> On Saturday 11 April 2009 22:54:12 Seth Mattinen wrote:
>> Spiro Harvey wrote:
>> > Personally, I would expect any sysadmins I hired to be capable of these
>> > basics.
>> <sarcasm>
>> Bah, you expect too much. One should expect to have the community do all
>> the work for you so there's more time to complain.
>> </sarcasm>
>> There's a few people that post to the c-nsp list that I just want to
>> strangle; they ask stupid questions like "tell me what to do with this
>> router I bought" and expect the list to write configs for them. It make
>> me die inside a little every time I see them ask a beyond basic
>> questions and that someone out there is probably paying them as a "Cisco
>> expert".
>> Now, back on topic. Debian is very deliberate about how things get
>> phased out. (Compared to, say, Fedora Core.) Anyone who pays attention
>> should know better. Anyone who's used Debian for any length of time
>> should know that when different versions of something show up, the old
>> one is most likely gone in the next release. If you want to run a legacy
>> system, by all means, but don't expect the community to focus on it.
>> ~Seth
> --
> To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: