Prev: Alt.OS.Linux.Slackware FAQ pointer
Next: begone (was: Re: gone)
From: Dario Niedermann on 4 Feb 2010 14:33
Has anyone noticed spurious stuff in their '/srv/httpd/htdocs' directory
after an httpd upgrade?

I've found a 'manual' directory and an 'index.html.new' file (containing
Apache's "it works!" page) in my site's root directory after the latest
security upgrade.

This doesn't seem right.


--
> head -n1 /etc/*-{version,release} && uname -moprs
Slackware 12.2.0
Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Lew Pitcher on 4 Feb 2010 14:39
On February 4, 2010 14:33, in alt.os.linux.slackware,
M8R-cthw2f(a)spamherelots.com wrote:

> Has anyone noticed spurious stuff in their '/srv/httpd/htdocs' directory
> after an httpd upgrade?
>
> I've found a 'manual' directory and an 'index.html.new' file (containing
> Apache's "it works!" page) in my site's root directory after the latest
> security upgrade.
>
> This doesn't seem right.

Slackware's httpd install package has done that for-ever. At least since
Slackware 3 days.

It used to bother me, as I'd have my (single, internal) website set up
in /var/www/htdocs/ and every upgrade of the httpd package would wipe out
some or all of my setup.

These days, I keep all my web stuff in a site-specific directory
(i.e. /var/www/htdocs.local) and manage my httpd.conf files accordingly.
This way, a software upgrade doesn't clobber my webpage directory, and I
can manage httpd configuration changes as I see fit.

HTH
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------


From: Dario Niedermann on 4 Feb 2010 18:58
Lew Pitcher <lpitcher(a)teksavvy.com> wrote:

> M8R-cthw2f(a)spamherelots.com wrote:
>
>> Has anyone noticed spurious stuff in their '/srv/httpd/htdocs' directory
>> after an httpd upgrade?
>> I've found a 'manual' directory and an 'index.html.new' file (containing
>> Apache's "it works!" page) in my site's root directory after the latest
>> security upgrade.
>> This doesn't seem right.
>
> Slackware's httpd install package has done that for-ever. At least since
> Slackware 3 days.
>
> It used to bother me, as I'd have my (single, internal) website set up
> in /var/www/htdocs/ and every upgrade of the httpd package would wipe out
> some or all of my setup.


OK, thanks for confirming the issue.


> These days, I keep all my web stuff in a site-specific directory
> (i.e. /var/www/htdocs.local) and manage my httpd.conf files accordingly.
> This way, a software upgrade doesn't clobber my webpage directory, and I
> can manage httpd configuration changes as I see fit.


I'll use another dir as my DocumentRoot. Weird design choice, though.


--
> head -n1 /etc/*-{version,release} && uname -moprs
Slackware 12.2.0
Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
 | 
Pages: 1
Prev: Alt.OS.Linux.Slackware FAQ pointer
Next: begone (was: Re: gone)