From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: possible bug in the squid config
Date: Wed, 23 Jan 2013 17:03:36 +0100 [thread overview]
Message-ID: <1358957016.1836.7.camel@hughes.tremer.info> (raw)
In-Reply-To: <50FFE427.6060500@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On Wed, 2013-01-23 at 14:22 +0100, Daniel Weismüller wrote:
> > WARNING: Bad configuration keyword: force 1
>
> The parameter force 1 is part of the /etc/squidclamav.conf
> I deleted it and the erroe is gone
I guess that this line was introduced when you have been playing with
using squidclam without loading content twice.
I cannot find it in the default configuration file.
> > Can't write-open /var/log/updatexlrator/checkdeaddl.lck: Permission
> > denied at /var/ipfire/updatexlrator/bin/checkdeaddl line 33.
>
> I've changed the owner of the file
> /var/log/updatexlrator/checkdeaddl.lck from root:root to squid:squid and
> the error is gone.
>
> It seems that the squid/squidclamav/updx works fine now but I'll have to
> take a longer look at it.
Please send in a patch to address this issue.
Michael
prev parent reply other threads:[~2013-01-23 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:58 Daniel Weismüller
2013-01-23 13:22 ` Daniel Weismüller
2013-01-23 16:03 ` Michael Tremer [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=1358957016.1836.7.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@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