public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <whytea@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Additional section for Squid logging in the squid wiki
Date: Fri, 16 Mar 2012 12:24:42 +0100	[thread overview]
Message-ID: <4F6322FA.10101@ipfire.org> (raw)
In-Reply-To: <E526BF64-3F0C-4594-8411-03398FE386C0@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

Hi Erik,
I like this idea.
There is already a log section in the wiki. Maybe you do a little work 
on the proxy-logs and proxy-reports wikis and please create a link to 
the proxy-reports in the proxy-wiki (calamaris).

thanks a lot

- Daniel

Am 16.03.2012 12:07, schrieb Erik K.:
> Hi all,
> i was thinking about to add a additional section for the logging in the squid wiki. Calamaris for example aren´t explained in the wiki, also a small excurse into the logging files access.log, cache.log and maybe the user_agent.log and the meanings can be helpful for the users to find out possible problems.
> I´am not sure if this will be too much for this wiki cause at this time it is already quiet big.
>
> What are you thinking about this ?
>
> Greetings
>
> Erik
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation

-- 
__________________________________________

You need a firewall?
Easy to use? Powerful? Modular? For free?

www.ipfire.org
An Open Source Firewall Solution


      reply	other threads:[~2012-03-16 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 11:07 Erik K.
2012-03-16 11:24 ` Daniel Weismüller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F6322FA.10101@ipfire.org \
    --to=whytea@ipfire.org \
    --cc=documentation@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox