THAT sounds reasonable but i miss where this is statet in the documentation?
with "LogLevel notice core:info" the first look is indeed a usable compromise, please state this example in the documentation, because i can not easily switch to the english one at least in the german it is missing - i hate Content Negotiation thank you! Am 08.02.2013 14:19, schrieb Mario Brandt: > the advantage is that you can define the log level for each module > > e.g. > > LogLevel warn ssl:error auth_digest:error socache_shmcb:warn > mpm_worker:warn fcgid:info > > I think with a little patience you can figure out the best log level > config for your needs. > > Cheers > Mario > > On 8 February 2013 13:17, Reindl Harald <[email protected]> wrote: > >> so because some guys was unhappy with this working behavior and did not >> want to use a higher LogLevel we now have to go the other direction and >> exlpode our logfiles or no way to take notice about wrong path's without >> grab trough access-logs which have sometimes a size of several GB which >> makes it hard to impossible to "cat them together" and have a single grep >> over some hundret of vhosts >> >> a way better solution would have been introduce a new LogLevel with 2.4
signature.asc
Description: OpenPGP digital signature
