On Fri, 03 Oct 2008 22:12:49 -0700
John Rudd <[EMAIL PROTECTED]> wrote:
>
>At the very least, when the config file and options change, the ClamAV
>team should post a notice which explicitly lists (and only lists):
>
>1) new config items
>2) removed config items
>3) config items whose syntax, sema
On 2008/10/04 12:50 PM Jerry wrote:
> From my experience, if an end user refuses to RTFM, adding additional
> reading material is not going to solve the problem. The needed
> documentation is all ready readily available. The motivation to fetch
> and read it are what is sorely lacking.
You're conf
I use clamav 0.94 on a SLED10 SP2 machine.
Upon manual update as root with
linux:~ # freshclam
the update of databases works fine
However trying editing /etc/boot.local with
/usr/sbin/rcfreshclam start
I get the confirming "done" as boot message and the
ps ax
confirms that the freshclam
Aecio F. Neto wrote:
> I don't agree with that, but let me put another option:
> 1) Break on unknown options
> 2) Ignore obsolete options and warn OP
>
> If any Op (or poor user) adds an option like
> PleaseClamAVCleanInfectedFilesForMe yes
> and expects it to work, are you really sure that the sof
Hi there,
On Sat, 4 Oct 2008 John Rudd wrote:
> ...what they REALLY ought to do is supply a tool which reads old
> config files, and does something like a lint check.
I believe there was a similar tool published by a user a while ago.
Why not put this in bugzilla as suggested by Tomasz? (I hav
- Original Message -
From: "Colin Alston" <[EMAIL PROTECTED]>
To: "ClamAV users ML"
Sent: Saturday, October 04, 2008 1:30 PM
Subject: Re: [Clamav-users] Stop it!
> On 2008/10/04 12:50 PM Jerry wrote:
>> From my experience, if an end user refuses to RTFM, adding additional
>> reading ma
On Fri, Oct 03, 2008 at 12:27:56PM +0200, Colin Alston said:
> I've had enough now, and I want all you ClamAV people to listen up.
>
> ClamAV has been continuously and repetitively adjusting configuration
> options in such a way that breaks anything which is automatically
> upgraded just stops wor
On Sat, Oct 4, 2008 at 9:04 AM, Sarocet <[EMAIL PROTECTED]> wrote:
> Aecio F. Neto wrote:
> > I don't agree with that, but let me put another option:
> > 1) Break on unknown options
> > 2) Ignore obsolete options and warn OP
> >
> > If any Op (or poor user) adds an option like
> > PleaseClamAVClea
Quoting "David F. Skoll" <[EMAIL PROTECTED]>:
> The principle of least surprise says ClamAV
> should reject that. By the same token, the principle of least surprise
> says that ClamAV should not break on previously-valid configuration files.
But it is a big surprise when the action that old line
Quoting "Aecio F. Neto" <[EMAIL PROTECTED]>:
> I don't agree with that, but let me put another option:
> 1) Break on unknown options
> 2) Ignore obsolete options and warn OP
Valid in many cases...
> If any Op (or poor user) adds an option like
> PleaseClamAVCleanInfectedFilesForMe yes
> and expe
Colin Alston wrote:
> On 2008/10/04 12:50 PM Jerry wrote:
>> From my experience, if an end user refuses to RTFM, adding additional
>> reading material is not going to solve the problem. The needed
>> documentation is all ready readily available. The motivation to fetch
>> and read it are what is so
Quoting Charles Gregory <[EMAIL PROTECTED]>:
> A lot of people seem to think it is 'proper' for a mis-configured server
> to just "die" or fail to start.
Yes, a lot of people do... :)
> This makes sense when the server has an
> *obvious* function/effect and its failure will be noted by interrupt
Eric Rostetter wrote:
> Quoting "Aecio F. Neto" <[EMAIL PROTECTED]>:
>
>> I don't agree with that, but let me put another option:
>> 1) Break on unknown options
>> 2) Ignore obsolete options and warn OP
>
> Valid in many cases...
>
>> If any Op (or poor user) adds an option like
>> PleaseClamAVC
Quoting Dennis Peterson <[EMAIL PROTECTED]>:
> Jose-Marcio's elegant J-Chkmail milter has a beautiful option. It will
> create a new config file using to the extent possible all your existing
> options. (That same tool can generate a clean config file that has all
> defaults filled in, too.) If ea
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Rostetter
> Sent: Saturday, October 04, 2008 12:44 PM
> To: clamav-users@lists.clamav.net
> Subject: Re: [Clamav-users] Handling of unknown
> configuration lines (was Re:Stop it!)
>
On Sat, 04 Oct 2008 08:32:42 -0700
Dennis Peterson <[EMAIL PROTECTED]> wrote:
>Colin Alston wrote:
>> On 2008/10/04 12:50 PM Jerry wrote:
>>> From my experience, if an end user refuses to RTFM, adding
>>> additional reading material is not going to solve the problem. The
>>> needed documentation i
Strange...
A boring thread whose subject is stop it, does not stop!
Tonino
Jerry ha scritto:
> On Sat, 04 Oct 2008 08:32:42 -0700
> Dennis Peterson <[EMAIL PROTECTED]> wrote:
>
>
>> Colin Alston wrote:
>>
>>> On 2008/10/04 12:50 PM Jerry wrote:
>>>
From my experience, if an e
Tonix (Antonio Nati) wrote:
> Strange...
>
> A boring thread whose subject is stop it, does not stop!
>
> Tonino
>
Thanks for playing!
dp
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
On Sat, Oct 4, 2008 at 12:29 PM, Eric Rostetter
<[EMAIL PROTECTED]>wrote:
> > If any Op (or poor user) adds an option like
> > PleaseClamAVCleanInfectedFilesForMe yes
> > and expects it to work, are you really sure that the software should not
> > ignore this?
>
> Yes. What happens if he means to
On Sat, 04 Oct 2008 18:39:08 +0200
"Tonix (Antonio Nati)" <[EMAIL PROTECTED]> wrote:
>A boring thread whose subject is stop it, does not stop!
Sorry about that. Perhaps I could interest you in the:
"Feature wish: "Virtual" POP3 folder with IMAP"
Now playing on the 'Dovecot' mailing list
On Fre, 2008-10-03 at 20:37 +0200, Colin Alston wrote:
> On 2008/10/03 05:57 PM James Kosin wrote:
> > Colin Alston wrote:
> >> I've had enough now, and I want all you ClamAV people to listen up.
> >
> > Hay, maybe the packagers could write a script or something to indicate a
> > problem with the
On Fre, 2008-10-03 at 16:56 -0400, Charles Gregory wrote:
> On Fri, 3 Oct 2008, David F. Skoll wrote:
> > That's not Clam's fault. On our product, if Clam dies, then mail is
> > tempfailed.
>
> I suppose you have 24/7 tech support. We go home on weekends. I don't need
> to tempfail all mail unti
On Sat, Oct 4, 2008 at 5:15 PM, Bernd Petrovitsch <[EMAIL PROTECTED]> wrote:
> > > users could take the appropriate action ASAP instead of finding out or
> > > having to check the logs on an hourly basis for problems.
> >
> > You're (by you I mean everyone agreeing here with how ClamAV fails)
> >
Eric Rostetter wrote:
>> The principle of least surprise says ClamAV
>> should reject that. By the same token, the principle of least surprise
>> says that ClamAV should not break on previously-valid configuration files.
> But it is a big surprise when the action that old line was supposed to ta
On 2008/10/04 10:15 PM Bernd Petrovitsch wrote:
>> users to sit and audit each change. On Ubuntu for example there can be
>> as many as 30 to 50 updates a week.
>
> Using a desktop distribution on a server was *your* decision. And you
> really *must* upgrade that much?
> Probably not really.
It'
Aecio F. Neto wrote:
> On Sat, Oct 4, 2008 at 5:15 PM, Bernd Petrovitsch <[EMAIL PROTECTED]> wrote:
>
users could take the appropriate action ASAP instead of finding out or
having to check the logs on an hourly basis for problems.
>>> You're (by you I mean everyone agreeing here with how
Dennis Peterson wrote:
> This seems a bit dramatic. Nobody is suffering. It takes but 10 minutes
> 3 or 4 times each year to visit and modify the ClamAV config files, if
> at all. Somebody's inner drama queen is getting the best of them here.
If you are managing one machined or a few identicall
David F. Skoll wrote:
> Dennis Peterson wrote:
>
>> This seems a bit dramatic. Nobody is suffering. It takes but 10 minutes
>> 3 or 4 times each year to visit and modify the ClamAV config files, if
>> at all. Somebody's inner drama queen is getting the best of them here.
>
> If you are managing
Jerry wrote:
>
> The sad part is that they will continue to blame others for their
> lackadaisical approach.
So, let me attempt to summarize your side of this here (and do correct
me if my summary is wrong, as I'm not trying to build a strawman argument).
You're justifying the laziness of the
On 2008/10/04 10:55 PM Dennis Peterson wrote:
> configuration problems. You need to classify those machines and knock
> off some class-based templates and be done with it. I don't see that as
> a vendor problem.
Of course it's a vendor problem! :) You even just said why. We'd have
to keep conti
On Sam, 2008-10-04 at 17:29 -0300, Aecio F. Neto wrote:
> On Sat, Oct 4, 2008 at 5:15 PM, Bernd Petrovitsch <[EMAIL PROTECTED]> wrote:
>
> > > > users could take the appropriate action ASAP instead of finding out or
> > > > having to check the logs on an hourly basis for problems.
> > >
> > > You'
On Sam, 2008-10-04 at 22:38 +0200, Colin Alston wrote:
> On 2008/10/04 10:15 PM Bernd Petrovitsch wrote:
> >> users to sit and audit each change. On Ubuntu for example there can be
> >> as many as 30 to 50 updates a week.
> >
> > Using a desktop distribution on a server was *your* decision. And y
Colin Alston wrote:
> On 2008/10/04 10:55 PM Dennis Peterson wrote:
>> configuration problems. You need to classify those machines and knock
>> off some class-based templates and be done with it. I don't see that as
>> a vendor problem.
>
> Of course it's a vendor problem! :) You even just said
On Sat, 04 Oct 2008 14:04:22 -0700
John Rudd <[EMAIL PROTECTED]> wrote:
>Jerry wrote:
>
>>
>> The sad part is that they will continue to blame others for their
>> lackadaisical approach.
>
>So, let me attempt to summarize your side of this here (and do correct
>me if my summary is wrong, as I'
Dennis Peterson wrote:
> If you don't feel like you're getting your money's worth then the thing
> to do is spend it somewhere else. Vote with your pocket book. That of
> course begs the question: Are you getting your money's worth?
Yes, I'm getting my money's worth out of Clam. But rejecting
Jerry wrote:
> 1) Learn to live with it.
A very fine attitude.
> 2) Write a patch/utility that suits your needs.
Forking software is expensive.
> 3) Write your own AV program
Even more expensive.
> 4) Use another AV program. There are several available, both OS/Free
> and commercial.
Even m
Jerry wrote:
> On Sat, 04 Oct 2008 14:04:22 -0700
> John Rudd <[EMAIL PROTECTED]> wrote:
>
>> Jerry wrote:
>>
>>> The sad part is that they will continue to blame others for their
>>> lackadaisical approach.
>> So, let me attempt to summarize your side of this here (and do correct
>> me if my s
We are getting somewhat off-topic but:
On Fre, 2008-10-03 at 20:56 +, reiner otto wrote:
[]
> Agreed. Unfortunately, this is a general problem with OpenSource.
> As a programmer for already over 30 years, I am still wondering that
> the terms "Usability, user-friendliness, egoless-program
--- Bernd Petrovitsch <[EMAIL PROTECTED]> schrieb am Sa, 4.10.2008:
Von: Bernd Petrovitsch <[EMAIL PROTECTED]>
Betreff: Re: [Clamav-users] Stop it!
An: "ClamAV users ML"
Datum: Samstag, 4. Oktober 2008, 22:09
We are getting somewhat off-topic but:
On Fre, 2008-10-03 at 20:56 +, reiner ott
39 matches
Mail list logo
