Hi folks,
Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg.
At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership,
Don't know if it is my actual config (previous one untouched anyway), but this is what i did to get it up and running in a CentOs 4.3 host
Thanks for your ideas
Jose
--------
[root@sparkbox ~]# yum update <...>
Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package clamav.i386 0:0.88.3-1.el4.rf set to be updated ---> Package clamav-db.i386 0:0.88.3-1.el4.rf set to be updated ---> Package clamd.i386 0:0.88.3-1.el4.rf set to be updated --> Running transaction check
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Installing: clamav i386 0.88.3-1.el4.rf rpmforge 724 k replacing clamav-lib.i386 0.88.2-2.el4.kb
clamav-db i386 0.88.3-1.el4.rf rpmforge 5.1 M replacing clamav-update.i386 0.88.2-2.el4.kb
clamd i386 0.88.3-1.el4.rf rpmforge 64 k replacing clamav-server.i386 0.88.2-2.el4.kb
Transaction Summary ============================================================================= Install 3 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 5.9 M Is this ok [y/N]: y Downloading Packages: (1/3): clamav-0.88.3-1.el 100% |=========================| 724 kB 00:01 (2/3): clamav-db-0.88.3-1 100% |=========================| 5.1 MB 00:11 (3/3): clamd-0.88.3-1.el4 100% |=========================| 64 kB 00:00 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: clamav-db ######################### [1/8] Installing: clamav [2/8]warning: /etc/freshclam.conf created as /etc/freshclam.conf.rpmnew Installing: clamav ######################### [2/8] Installing: clamd ######################### [3/8] Cleanup : clamav ######################### [4/8] Removing : clamav-lib ######################### [5/8] warning: /etc/sysconfig/freshclam saved as /etc/sysconfig/freshclam.rpmsave warning: /etc/cron.d/clamav-update saved as /etc/cron.d/clamav-update.rpmsave Removing : clamav-update ######################### [6/8] warning: /var/lib/clamav/main.cvd saved as /var/lib/clamav/main.cvd.rpmsave warning: /var/lib/clamav/daily.cvd saved as /var/lib/clamav/daily.cvd.rpmsave Removing : clamav-data ######################### [7/8] Removing : clamav-server ######################### [8/8]
Installed: clamav.i386 0:0.88.3-1.el4.rf clamav-db.i386 0:0.88.3-1.el4.rf clamd.i386 0:0.88.3-1.el4.rf Replaced: clamav-data.i386 0:0.88.2-2.el4.kb clamav-lib.i386 0:0.88.2-2.el4.kb clamav-server.i386 0:0.88.2-2.el4.kb clamav-update.i386 0:0.88.2-2.el4.kb Complete!
[root@sparkbox ~]# service clamd start Starting Clam AntiVirus Daemon: ERROR: Can't get information about user clamav.
[FALLÓ] [root@sparkbox ~]# cp /etc/freshclam.conf /etc/freshclam.conf.old [root@sparkbox ~]# cp /etc/freshclam.conf.rpmnew /etc/freshclam.conf cp: ¿sobreescribir «/etc/freshclam.conf»? (s/n) s [root@sparkbox ~]# groupadd clamav [root@sparkbox ~]# useradd -g clamav -s /sbin/nologin -c "Clam AntiVirus" clamav [root@sparkbox ~]# service clamd start Starting Clam AntiVirus Daemon: [ OK ]
[root@smarteyebox yum.repos.d]# freshclam -v ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!). ERROR: Problem with internal logger.
[root@sparkbox ~]# l /var/log/clamav/ drwxr-xr-x 2 104 105 4,0K jul 3 10:32 clamav/ <...>
[root@sparkbox ~]# chown -R clamav.clamav /var/log/clamav/
[root@sparkbox ~]# freshclam -v Current working dir is /var/clamav Max retries == 3 ClamAV update process started at Mon Jul 3 10:47:04 2006 Querying current.cvd.clamav.net TTL: 103 Software version from DNS: 0.88.3 main.cvd version from DNS: 39 main.cvd is up to date (version: 39, sigs: 58116, f-level: 8, builder: tkojm) daily.cvd version from DNS: 1579 daily.cvd is up to date (version: 1579, sigs: 2627, f-level: 8, builder: sven) Freeing option list...done
[root@sparkbox ~]# clamscan /root/.xauthv1YQ7D: OK /root/.rpmmacros: OK /root/.festival_history: OK /root/.bash_history: OK /root/.xauthyIE3tF: OK /root/.gtkrc-1.2-gnome2: OK /root/.xauthrr5vmv: OK /root/.bash_profile: OK <...> ----------- SCAN SUMMARY ----------- Known viruses: 60743 Engine version: 0.88.3 Scanned directories: 1 Scanned files: 54 Infected files: 0 Data scanned: 0.18 MB Time: 2.030 sec (0 m 2 s)
[sm0ketst@sparkbox ~]$ clamscan /home/sm0ketst/.signature.tag: OK /home/sm0ketst/.rpmmacros: OK /home/sm0ketst/soundconverter.log: OK <...>
On Mon, 2006-07-03 at 11:04 +0200, J.J.Garcia wrote:
Hi folks,
Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg.
At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership,
Don't know if it is my actual config (previous one untouched anyway), but this is what i did to get it up and running in a CentOs 4.3 host
Thanks for your ideas
Jose
[root@sparkbox ~]# yum update <...>
Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package clamav.i386 0:0.88.3-1.el4.rf set to be updated ---> Package clamav-db.i386 0:0.88.3-1.el4.rf set to be updated ---> Package clamd.i386 0:0.88.3-1.el4.rf set to be updated --> Running transaction check
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Installing: clamav i386 0.88.3-1.el4.rf rpmforge 724 k replacing clamav-lib.i386 0.88.2-2.el4.kb
clamav-db i386 0.88.3-1.el4.rf rpmforge 5.1 M replacing clamav-update.i386 0.88.2-2.el4.kb
clamd i386 0.88.3-1.el4.rf rpmforge 64 k replacing clamav-server.i386 0.88.2-2.el4.kb
Transaction Summary
Install 3 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 5.9 M Is this ok [y/N]: y Downloading Packages: (1/3): clamav-0.88.3-1.el 100% |=========================| 724 kB 00:01 (2/3): clamav-db-0.88.3-1 100% |=========================| 5.1 MB 00:11 (3/3): clamd-0.88.3-1.el4 100% |=========================| 64 kB 00:00 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: clamav-db ######################### [1/8] Installing: clamav [2/8]warning: /etc/freshclam.conf created as /etc/freshclam.conf.rpmnew Installing: clamav ######################### [2/8] Installing: clamd ######################### [3/8] Cleanup : clamav ######################### [4/8] Removing : clamav-lib ######################### [5/8] warning: /etc/sysconfig/freshclam saved as /etc/sysconfig/freshclam.rpmsave warning: /etc/cron.d/clamav-update saved as /etc/cron.d/clamav-update.rpmsave Removing : clamav-update ######################### [6/8] warning: /var/lib/clamav/main.cvd saved as /var/lib/clamav/main.cvd.rpmsave warning: /var/lib/clamav/daily.cvd saved as /var/lib/clamav/daily.cvd.rpmsave Removing : clamav-data ######################### [7/8] Removing : clamav-server ######################### [8/8]
Installed: clamav.i386 0:0.88.3-1.el4.rf clamav-db.i386 0:0.88.3-1.el4.rf clamd.i386 0:0.88.3-1.el4.rf Replaced: clamav-data.i386 0:0.88.2-2.el4.kb clamav-lib.i386 0:0.88.2-2.el4.kb clamav-server.i386 0:0.88.2-2.el4.kb clamav-update.i386 0:0.88.2-2.el4.kb Complete!
[root@sparkbox ~]# service clamd start Starting Clam AntiVirus Daemon: ERROR: Can't get information about user clamav.
[FALLÓ] [root@sparkbox ~]# cp /etc/freshclam.conf /etc/freshclam.conf.old [root@sparkbox ~]# cp /etc/freshclam.conf.rpmnew /etc/freshclam.conf cp: ¿sobreescribir «/etc/freshclam.conf»? (s/n) s [root@sparkbox ~]# groupadd clamav [root@sparkbox ~]# useradd -g clamav -s /sbin/nologin -c "Clam AntiVirus" clamav [root@sparkbox ~]# service clamd start Starting Clam AntiVirus Daemon: [ OK ]
[root@smarteyebox yum.repos.d]# freshclam -v ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!). ERROR: Problem with internal logger.
[root@sparkbox ~]# l /var/log/clamav/ drwxr-xr-x 2 104 105 4,0K jul 3 10:32 clamav/ <...>
[root@sparkbox ~]# chown -R clamav.clamav /var/log/clamav/
[root@sparkbox ~]# freshclam -v Current working dir is /var/clamav Max retries == 3 ClamAV update process started at Mon Jul 3 10:47:04 2006 Querying current.cvd.clamav.net TTL: 103 Software version from DNS: 0.88.3 main.cvd version from DNS: 39 main.cvd is up to date (version: 39, sigs: 58116, f-level: 8, builder: tkojm) daily.cvd version from DNS: 1579 daily.cvd is up to date (version: 1579, sigs: 2627, f-level: 8, builder: sven) Freeing option list...done
[root@sparkbox ~]# clamscan /root/.xauthv1YQ7D: OK /root/.rpmmacros: OK /root/.festival_history: OK /root/.bash_history: OK /root/.xauthyIE3tF: OK /root/.gtkrc-1.2-gnome2: OK /root/.xauthrr5vmv: OK /root/.bash_profile: OK <...> ----------- SCAN SUMMARY ----------- Known viruses: 60743 Engine version: 0.88.3 Scanned directories: 1 Scanned files: 54 Infected files: 0 Data scanned: 0.18 MB Time: 2.030 sec (0 m 2 s)
[sm0ketst@sparkbox ~]$ clamscan /home/sm0ketst/.signature.tag: OK /home/sm0ketst/.rpmmacros: OK /home/sm0ketst/soundconverter.log: OK <...>
You are mixing 2 different clamav builds ... one is coming from Dag Wieers' EL4 repo ... the other is coming from KBS-CentOS-Extras repo. Dag's packages are built from the RPMForge spec file, KBS is built from a different spec file (from Fedora Extras).
Both of these clamav builds work fine ... but they are different and don't work well together.
Pick one repo to do clamav from ... in the other one, inside the repo definition for that repo, do this:
exclude=clamd clamav*
That should take care of dualing repo problems for clamav.
Thanks, Johnny Hughes
Johnny Hughes wrote:
On Mon, 2006-07-03 at 11:04 +0200, J.J.Garcia wrote:
Hi folks,
Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg.
At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership,
Don't know if it is my actual config (previous one untouched anyway), but this is what i did to get it up and running in a CentOs 4.3 host
Thanks for your ideas
Jose
You are mixing 2 different clamav builds ... one is coming from Dag Wieers' EL4 repo ... the other is coming from KBS-CentOS-Extras repo. Dag's packages are built from the RPMForge spec file, KBS is built from a different spec file (from Fedora Extras).
Both of these clamav builds work fine ... but they are different and don't work well together.
Pick one repo to do clamav from ... in the other one, inside the repo definition for that repo, do this:
exclude=clamd clamav*
That should take care of dualing repo problems for clamav.
Thanks, Johnny Hughes
Is that a provisional issue?
I mean, IMHO there's no point in maintaining this two releases of the same thing/pkg in different repositories, unless you name them different to be seleccted as appropiate (not exclude tag involved).
If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
TIA for your time,
Jose.
On Mon, 2006-07-03 at 12:51 +0200, J.J.Garcia wrote:
Johnny Hughes wrote:
On Mon, 2006-07-03 at 11:04 +0200, J.J.Garcia wrote:
Hi folks,
Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg.
At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership,
Don't know if it is my actual config (previous one untouched anyway), but this is what i did to get it up and running in a CentOs 4.3 host
Thanks for your ideas
Jose
You are mixing 2 different clamav builds ... one is coming from Dag Wieers' EL4 repo ... the other is coming from KBS-CentOS-Extras repo. Dag's packages are built from the RPMForge spec file, KBS is built from a different spec file (from Fedora Extras).
Both of these clamav builds work fine ... but they are different and don't work well together.
Pick one repo to do clamav from ... in the other one, inside the repo definition for that repo, do this:
exclude=clamd clamav*
That should take care of dualing repo problems for clamav.
Thanks, Johnny Hughes
Is that a provisional issue?
I mean, IMHO there's no point in maintaining this two releases of the same thing/pkg in different repositories, unless you name them different to be seleccted as appropiate (not exclude tag involved).
If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
TIA for your time,
Jose.
I can't ever remember upgrading clamav where I did not have to change file permissions on the log files. It's never been a problem...rather just something I do. I even wrote a little howto about it on my site.
you don't take it's life just because it can't do one thing
John Rose
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Is that a provisional issue?
I mean, IMHO there's no point in maintaining this two releases of the same thing/pkg in different repositories, unless you name them different to be seleccted as appropiate (not exclude tag involved).
These aren't centos repositories. We don't maintain them and they do not come from the .centos.org domain. Dag does the rpmforge.net repository and is receptive to input from the community as to what packages they'd like to see. Karanbir maintains his own project which is a rebuild of fedora extras for Centos. The more repositories you add, the more duplication you're likely to run into. This is why what Johnny suggested above is a good idea.
If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
A few. yum --disablerepo * --enablerepo rpmforge list available > dag yum --disablerepo * --enablerepo kbs-extras list available > kbs
then have a look through and compare the two.
Jim Perrin wrote:
Is that a provisional issue?
I mean, IMHO there's no point in maintaining this two releases of the same thing/pkg in different repositories, unless you name them different to be seleccted as appropiate (not exclude tag involved).
These aren't centos repositories. We don't maintain them and they do not come from the .centos.org domain. Dag does the rpmforge.net repository and is receptive to input from the community as to what packages they'd like to see. Karanbir maintains his own project which is a rebuild of fedora extras for Centos. The more repositories you add, the more duplication you're likely to run into. This is why what Johnny suggested above is a good idea.
Sure, i start thinking it's the best option in the actual environment.
If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
A few. yum --disablerepo * --enablerepo rpmforge list available > dag yum --disablerepo * --enablerepo kbs-extras list available > kbs
then have a look through and compare the two.
I take note,
Thx Jim & John
On Mon, 2006-07-03 at 15:51 +0200, J.J.Garcia wrote:
Jim Perrin wrote:
<snip> If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
A few. yum --disablerepo * --enablerepo rpmforge list available > dag yum --disablerepo * --enablerepo kbs-extras list available > kbs
then have a look through and compare the two.
And do it again in a few weeks, and do it again in a few weeks, and ... :-)
Actually it's not that bad but there is no telling, from within this project, when external repositories will gleefully commence stepping on each other. They address potentially different user communities with some degree of overlap.
I take note,
Thx Jim & John
<snip sig stuff>
On Mon, 2006-07-03 at 12:51 +0200, J.J.Garcia wrote:
Johnny Hughes wrote:
On Mon, 2006-07-03 at 11:04 +0200, J.J.Garcia wrote:
Hi folks,
Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg.
At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership,
Don't know if it is my actual config (previous one untouched anyway), but this is what i did to get it up and running in a CentOs 4.3 host
Thanks for your ideas
Jose
You are mixing 2 different clamav builds ... one is coming from Dag Wieers' EL4 repo ... the other is coming from KBS-CentOS-Extras repo. Dag's packages are built from the RPMForge spec file, KBS is built from a different spec file (from Fedora Extras).
Both of these clamav builds work fine ... but they are different and don't work well together.
Pick one repo to do clamav from ... in the other one, inside the repo definition for that repo, do this:
exclude=clamd clamav*
That should take care of dualing repo problems for clamav.
Thanks, Johnny Hughes
Is that a provisional issue?
I mean, IMHO there's no point in maintaining this two releases of the same thing/pkg in different repositories, unless you name them different to be seleccted as appropiate (not exclude tag involved).
Well ... there are reasons, dependencies with other packages within the repo is the main one.
Dag has his specs that work on many things ... then there is Fedora Extras (which is what KBS rebuilds) that are specifically for fedora.
I'm sure Dag has his reasons for not using the Fedora Extras spec file ... and KBS is rebuilding Fedora Extras, so he needs it as a dependency to meet requirements.
I don't think that we want repos where you have to have Dag _AND_ KBS enabled to meet requirements ... they should stand alone. (or at least have all reqts met with Base and the repo) ...
That means that there will be overlap ... and that means there will be problem packages from time to time.
If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
On Mon, 3 Jul 2006, J.J.Garcia wrote:
I mean, IMHO there's no point in maintaining this two releases of the same thing/pkg in different repositories, unless you name them different to be seleccted as appropiate (not exclude tag involved).
If so, how many pkgs are going to be like this way? It seems to me it could be a nightmare, but this is only my opinion. Hints allowed.
You should really talk to the Fedora people about this because they decided to do it differently than what was available at the time. I've been making clamav packages at least a year before them.
But then again, they probably blame me for not joining the Fedora process and, well, I guess they've become upstream now...
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
-
Dag Wieers -
J.J.Garcia -
Jim Perrin -
Johnny Hughes -
rado -
William L. Maltby