To facilitate bandwidth issues, I've set up an internal clam proxy server on
SLES15 running the 103.x client. I have successfully connected to it using a
different SLES15 box also running the 103.x client and downloaded updates to it.
However, I still have an older SLES11 box running the 98.x cl
On Dec 2, 2021, at 11:08, novpenguincne via clamav-users
> > clamav-users@lists.clamav.net wrote:
> >
> > To facilitate bandwidth issues, I've set up an internal clam proxy server
> > on SLES15 running the 103.x client. I have successfully connected to it
> >
version that is currently supported is the 0.101.x line, but that
> will be EOL in January. So I would recommend 0.103.x or higher.
>
> —
>
> Sent from my iPad
>
> > On Dec 2, 2021, at 13:10, novpenguincne via clamav-users
> > clamav-users@lists.clamav.net wrote:
&g
Thanks Andrew. I am trying that now. This being an older 32-bit o/s, it has
been difficult to track down the full rpm install so I've been trying to
install from source. But of course that means running into dependency issues.
I'll keep working on it for a bit to see if I can work through th
ot;
>
> That have to be edited but I have no issues with signatures, operation or
>
> stability.
>
> I am using
>
> openssl-1.1.1g
>
> curl-7.73.0
>
> zlib-1.2.11
>
> If you are not comfortable building the packages needed in non standard
>
> locations
> >
> > /opt/openssl-1.1.1g)
> >
> > There are also 4 make files that will trigger -W errors
> >
> > "-Wno-logical-op-parentheses" "-Wno-dangling-else"
> >
> > That have to be edited but I have no issues with signatures, operation or
Here is where I'm at trying to get clam to run on an older 32-bit O/S.
After testing the install (from source) of every version between 99 and 104,
the highest level version that I could get to successfully install was 100.
Once I try 101 or higher, there are just too many dependency issues to
, G.W. Haywood
wrote:
> Hi there,
>
> On Thu, 9 Dec 2021, novpenguincne via clamav-users wrote:
>
> > Here is where I'm at trying to get clam to run on an older 32-bit O/S.
>
> Whether it's 32 bit or 64 bit shold not be an issue. The age of the OS
>
> is a signi
I'm still experimenting with Clam and I've got 103.4 installed on an OEL 7.9
box. I've got freshclam configured to download new updates every few hours. I
can manually run freshclam and successfully receive updates and I can manually
run clamscan successfully.
If I run a ps command, I see /usr/
OEL = Oracle Enterprise Linux
Under /usr/lib/systemd/system, there are the four clam*.service files. But
since none of them are active or enabled, I don't think can be the source. I
scanned the entire file system for cl*.service and they are the only ones I can
find.
It's not a big issue. I
That's it! Under /etc/crond.d, there is a clamav-update cron that runs
freshclam-sleep every 3 hours. So this overrides the frequency setting in the
freshclam.conf file.
Mystery solved. I checked for cron jobs but I only looked in /var/spool/cron
and didn't think to check in /etc/crond.d.
Than
11 matches
Mail list logo
