Am 09.06.2016 um 15:10 schrieb Bill Cole:
stream(127.0.0.1@1858): OK.
That should have been your strongest clue: "stream(127.0.0.1@1858)" is
clearly describing a connection via TCP on localhost, not a socket node
in the filesystem
i doubt that anything is "clearly" in that context - look in
On 8 Jun 2016, at 9:42, Carlo Manuali wrote:
It works with no changes by using TCP socket (on localhost).
—Carlo
On 8 Jun 2016, at 6:02, Carlo Manuali wrote:
In particular I’ve adopted the local mode, that uses a local socket
(file) in order to establish the communication between them.
[..
It works with no changes by using TCP socket (on localhost).
—Carlo
> On 08 Jun 2016, at 14:48, Carlo Manuali wrote:
>
> I did all but I did not solve the problem so I will better investigate
> alternative causes.
>
> I suppose something went wrong when SA tries to load the plugin (by accessin
I did all but I did not solve the problem so I will better investigate
alternative causes.
I suppose something went wrong when SA tries to load the plugin (by accessing
clamav.cf and/or clamav.pm) during the startup process only.
At this point probably is not a time-related issue.
Thank you Ha
Am 08.06.2016 um 13:49 schrieb Carlo Manuali:
I wrote a init-script as follows (S20clamd followed by other services
then S78SpamAssassin) but nothing has changed (in the meantime all the
daemons and services are up and running).
On top of all, just re-running "/etc/init.d/SpamAssassin restart"
I wrote a init-script as follows (S20clamd followed by other services then
S78SpamAssassin) but nothing has changed (in the meantime all the daemons and
services are up and running).
On top of all, just re-running "/etc/init.d/SpamAssassin restart" from shell
the system starts working.
Any ot
Am 08.06.2016 um 12:58 schrieb Carlo Manuali:
yes, 6.7.
I totally agree with you, but unfortunately I can’t change a system in
production now.
Any other ideas?
try to implement something like
"ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID" in the
mysqld-unit after starting clamd,
Catlo
> /usr/local/sbin/clamd && /etc/init.d/spamassassin restart
If you are using init.d for SA, you should also use it for ClamAV. Using
a consistent startup system will certainly go in the right direction.
Olivier
yes, 6.7.
I totally agree with you, but unfortunately I can’t change a system in
production now.
Any other ideas?
—Carlo
> On 08 Jun 2016, at 12:53, Reindl Harald wrote:
>
>
>
> Am 08.06.2016 um 12:33 schrieb Carlo Manuali:
>> yes, I’m using scientific linux, fedora/redhat in other words.
Am 08.06.2016 um 12:33 schrieb Carlo Manuali:
yes, I’m using scientific linux, fedora/redhat in other words. I also tried:
which version - sounds like 6 or older when someone is talking about
/etc/init.d/
/usr/local/sbin/clamd && /etc/init.d/spamassassin restart
in rc.local (-> S99local
yes, I’m using scientific linux, fedora/redhat in other words. I also tried:
/usr/local/sbin/clamd && /etc/init.d/spamassassin restart
in rc.local (-> S99local in /etc/rc3.d/ )with no success.
Cheers,
—Carlo
> On 08 Jun 2016, at 12:11, Reindl Harald wrote:
>
>
>
> Am 08.06.2016 um 12:02 sch
Am 08.06.2016 um 12:02 schrieb Carlo Manuali:
I’ve installed the ClamAV plugin (v1.93, with v0.99.2 as ClamAV engine)
according to: https://wiki.apache.org/spamassassin/ClamAVPlugin. All has gone
well, it works.
In particular I’ve adopted the local mode, that uses a local socket (file) in
o
Hi Carlo,
> - I tried to put clamd on rc.local then moving SpamAssassin after: all
> the services started but the plugin do not "attach the daemon” (no
> filtering viruses);
You should start by mentionning what OS you are using, because the way
to start a service vaies greatly on one system or on
13 matches
Mail list logo
