Apache2 now default???

t011 · Tux's lil' helper Joined: 05 Sep 2002 Posts: 102

It appears as though Apache2 was unmasked today(July 12th) for x86. That's all well and good, but what are the implications of making that upgrade? Are my old config files compatible? What about the various modules? Do they need to be recompiled for Apache2? It just seems like there should be some kind of a warning for this change. Why can't the apache2 USE variable select whether you want the 2.x series versus the 1.3.x series? Of course, maybe I'm blowing this out of proportion. I really have no idea how different Apache2 is from the 1.3.x series.

zhenlin · Veteran Joined: 09 Nov 2002 Posts: 1361

They announced the unmasking on Friday... Of course, the announcement was overshadowed by the GLSAs...

t011 · Tux's lil' helper Joined: 05 Sep 2002 Posts: 102

Thanks. I now see the notice in the "News & Announcements" forum. The odd thing about the notice is that I'm subscribed to the gentoo-announce mailing list and I didn't receive the email. But then, all the GLSA's are listed as going to the gentoo-security mailing list, which I'm not subscribed to, but I received all those. What is going on with that news and announcements forum?!

zhenlin · Veteran Joined: 09 Nov 2002 Posts: 1361

There are some forum announcements that are not from [gentoo-announce]. The GLSAs belong to [gentoo-announce] not [gentoo-security].

puggy · Posted: Sun Jul 13, 2003 5:46 am Post subject:

I've just made the crossover from apache to apache2, it was remarkably painless actually. I just emerged apache2, removed apache from my default runlevel and stopped the server, changed my servername and a couple of other tweaks (Which were basically the same as in my apache.conf). I had to re-emerge mod_php (and add -D PHP4 to the /etc/conf.d/apache2 file) after adding apache2 to my USE flags, then I just added it to my default runlevel and launched apach2. Works fine so far.

One question...

I notice in the old /etc/conf.d/apache I have

volumen1 · Guru Joined: 01 Mar 2003 Posts: 393 Location: Missoula, MT

You were getting close. What I did was copy the content from /etc/apache/conf/addon-modules/mailman.conf right into my /etc/apache2/apache2.conf and that seemed fix it.... a little.

Now, I can access the mailman CGIs by using /mailman/admin/listname, however, Mailman is telling me that I have no lists. If I 'su - mailman' and then do a './bin/list_lists' it shows me that I still have my lists, phew. I'm not sure what I'm missing, though.

slartibartfasz · Posted: Mon Jul 14, 2003 10:33 pm Post subject:

FYI - the '-D foo' just sets a flag that triggers the loading of a module in the files in /etc/apache2/conf/modules.d - the code in the <IfDefine foo> containers only gets executed if u start apache2 with -D foo
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be.

puggy · Posted: Wed Jul 16, 2003 12:22 pm Post subject:

I've got it up and running under apache2 also, but I had to completely unemerge mailman, remove all its configuration files from /usr/local/mailman, then re-emerge it and set it up from scratch. I don't know if this was specifically an upgrade from apache and to apache2 problem however.

Puggy
_________________
Where there's open source , there's a way.

volumen1 · Guru Joined: 01 Mar 2003 Posts: 393 Location: Missoula, MT

I got it working. The old ebuilds put all the files in /var/mailman. This was the mailman user's home directory. In the new ebuild, this directory has been changed to /usr/local/mailman. The ebuild tries to copy some of your config files over, but they don't get your lists (that is /var/mailman/lists doesn't get copied to /usr/local/mailman/lists). So, I just copied over everything from /var/mailman to /usr/local/mailman. Then I needed to edit /etc/mail/aliases and change everything there to /usr/local/mailman and I was goodtimes.