Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] apache vhosts logging
- Date: Tue, 14 Jul 2015 19:15:43 +0900
- From: Kalin KOZHUHAROV <me.kalin@example.com>
- Subject: Re: [tlug] apache vhosts logging
- References: <CAKXLc7ejnGexFonXcaVAe_nYd5o287yHxfVP+A8h6m0fKEPM4w@mail.gmail.com> <20150714095135.GA22415@scott1.scottro.net>
On Tue, Jul 14, 2015 at 6:51 PM, Scott Robbins <scottro@example.com> wrote: > On Tue, Jul 14, 2015 at 06:31:30PM +0900, Kalin KOZHUHAROV wrote: >> Has anyone tried to use single access_log for several (but NOT all) >> VirtualHosts? >> >> e.g. >> >> <VirtualHost 10.1.1.1:80> >> CustomLog /var/log/access_log >> .... >> </VirtualHost> >> >> <VirtualHost 10.2.2.2:81> >> CustomLog /var/log/access_log >> .... > > > The silly question--is there a good reason to not use separate logs? > It is not a silly question, it is a normal IT question. My question is actually more of a security concern actually. > That being said, we've had hosts where we didn't set up separate logs, > everything writing to /var/log/httpd_access.log or similar and it never > broke anything that we saw. > I assume that is a special case, since you only have one "CustomLog" directive, it is supposed to work and I often use it. That is why I highlighted the NOT in "single access_log for several (but NOT all) VirtualHosts"... Cheers, Kalin.
- Follow-Ups:
- Re: [tlug] apache vhosts logging
- From: Scott Robbins
- References:
- [tlug] apache vhosts logging
- From: Kalin KOZHUHAROV
- Re: [tlug] apache vhosts logging
- From: Scott Robbins
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] apache vhosts logging
- Next by Date: Re: [tlug] Program to Save / Remap Bad Sectors
- Previous by thread: Re: [tlug] apache vhosts logging
- Next by thread: Re: [tlug] apache vhosts logging
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links