Dennis Peterson wrote:
>
> Is it really necessary to use clamscan? It has a lot working against it.
>
I am not using clamd since it kept dying one me, so until I look into it
in more detail I want the slower but reliable clamscan. I am running it
via sendmail/mimedfang software.
Andrew
___
Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson:
>Matthias Schmidt wrote:
>> Hello,
>>
>> I have a little problem with clamd:
>> the process terminates, because:
>> Socket file /tmp/clamd is in use by another process.
>>
>> now I have no glue, which other process could use th
matthias,
use the launchctl unload command, then remove the socket file, then
restart the server.
usually this should clean out the problems.
oliver
Am 24.09.2007 um 12:10 schrieb Matthias Schmidt:
> Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson:
>
>> Matthias Schmidt w
Hello Oliver,
Am/On Mon, 24 Sep 2007 12:20:08 +0200 schrieb/wrote Oliver Schwarz:
>matthias,
>
>use the launchctl unload command, then remove the socket file, then
>restart the server.
>usually this should clean out the problems.
well, I just killed clamd and restarted it with launchctl load -
look into the config file of clamav. there's an option which lets it
fix stale sockets.
cheerio
oliver
Am 24.09.2007 um 12:38 schrieb Matthias Schmidt:
> Hello Oliver,
>
> Am/On Mon, 24 Sep 2007 12:20:08 +0200 schrieb/wrote Oliver Schwarz:
>
>> matthias,
>>
>> use the launchctl unload command
Hello,
The /var/spool/mail/root log files on our servers are logging every file
that clamav scans, causing the files to become huge. I don't see what
in our clamd.conf configuration files would be causing this. Our
configuration file follows - any help would be appreciated.
##
## Config file
On 9/24/07, McGlynn, Sean (DOB) <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The /var/spool/mail/root log files on our servers are logging every file
> that clamav scans, causing the files to become huge. I don't see what
> in our clamd.conf configuration files would be causing this. Our
> configurati
On Mon, Sep 24, 2007 at 08:20:30AM -0400, McGlynn, Sean (DOB) said:
> Hello,
>
> The /var/spool/mail/root log files on our servers are logging every file
> that clamav scans, causing the files to become huge. I don't see what
> in our clamd.conf configuration files would be causing this. Our
>
Rob,
Thank you for your reply.
So to be clear, cron is calling a script (below). I assume even though
cron is calling a script, rather than the individual commands in the
script, your same suggestion applies? If so, would it be a matter of
adding 1>/dev/null to the end of each line? I'm somewh
On 20 Sep 07, at 2203, [EMAIL PROTECTED] wrote:
> -- Trog said the following on 9/19/07 2:55 PM:
>> Forth alternative: use current SVN code, which has it's own regex
>> code to
>> overcome platform issues.
>
> Compiled smoothly for me on Solaris 10 x86. It's now running on test
> box. Thanks fo
On 9/24/07, McGlynn, Sean (DOB) <[EMAIL PROTECTED]> wrote:
> Rob,
>
> Thank you for your reply.
>
> So to be clear, cron is calling a script (below). I assume even though
> cron is calling a script, rather than the individual commands in the
> script, your same suggestion applies? If so, would it
McGlynn, Sean (DOB) wrote:
> Hello,
>
> The /var/spool/mail/root log files on our servers are logging every file
> that clamav scans, causing the files to become huge. I don't see what
> in our clamd.conf configuration files would be causing this. Our
> configuration file follows - any help wou
Good Morning folks.
I have an automated scan system set up, and today I got a strange error.
*** stack smashing detected ***: clamscan terminated
First time I've ever seen this error.
So I ran the scan manually. This particular scan was going against root, so I
ran it manually.
after a while
Rob,
Thank you again for taking the time to reply, and for providing two
useful alternative. The first worked perfectly, and I believe I'll try
the second as it would be a much simpler script over all.
Thanks again.
Sean
This e-mail, i
On Mon, 24 Sep 2007, [EMAIL PROTECTED] wrote:
> after a while I get this:
>
> /sys/devices/pci:00/:00:06.0/config: OK
> /sys/devices/pci:00/:00:06.0/:17:00.0/host1/sfp: OK
> /sys/devices/pci:00/:00:06.0/:17:00.0/host1/vpd: Empty file
> /sys/devices/pci:00/:
Thanks to all who replied. I received an excellent suggestion from Rob
that resolved the issue.
This e-mail, including any attachments, may be confidential, privileged or
otherwise legally protected. If you have received this e-mail in e
Dennis Peterson wrote:
> McGlynn, Sean (DOB) wrote:
>> Hello,
>>
>> The /var/spool/mail/root log files on our servers are logging every file
>> that clamav scans, causing the files to become huge. I don't see what
>> in our clamd.conf configuration files would be causing this. Our
>> configurat
On 9/24/07, Christopher X. Candreva <[EMAIL PROTECTED]> wrote:
> On Mon, 24 Sep 2007, [EMAIL PROTECTED] wrote:
>
> > after a while I get this:
> >
> > /sys/devices/pci:00/:00:06.0/config: OK
> > /sys/devices/pci:00/:00:06.0/:17:00.0/host1/sfp: OK
> > /sys/devices/pci:00/
I'll do that tomorrow. But yes I agree it shouldn't trigger that error, which
was the other reason I posted it.
"Török Edvin" <[E
19 matches
Mail list logo
