Re: [CentOS] CentOS 6.3: libreport/abrt update problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mogens Kjaer said the following on 01/02/2013 07:52: > In updates, there are new packages of abrt and libreport. But yum update > gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates) Confirmed. Same issue here. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Xerox never comes up with anything original. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlELcBEACgkQ3kWu7Tfl6ZQCaACgyL3cYJfkP3Wi9quz2Os0NkAv JaMAoLCz/p7NQGYg3rxSniWMKBnTZ370 =DDQs -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6.3: libreport/abrt update problem
On Thu, Jan 31, 2013 at 10:52 PM, Mogens Kjaer wrote: > Hello, > > In updates, there are new packages of abrt and libreport. > > But yum update gives me: > > Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates) > Requires: libreport >= 2.0.9-5.el6_3.2 > Removing: libreport-2.0.9-5.el6.centos.x86_64 (@base) > libreport = 2.0.9-5.el6.centos > Updated By: libreport-2.0.9-5.el6.centos.2.x86_64 (updates) > libreport = 2.0.9-5.el6.centos.2 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > Is the new libreport incorrectly named > > libreport-2.0.9-5.el6.centos.2.x86_64 > > instead of: > > libreport-2.0.9-5.el6.2.x86_64 > > or is the dependency of abrt incorrect? > > Mogens abrt does requires libreport >= 2.0.9-5.el6_3.2. Problem seems to be that 2.0.9-5.el6.centos.2 is older than 2.0.9-5.el6_3.2 . Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 6.3: libreport/abrt update problem
Hello, In updates, there are new packages of abrt and libreport. But yum update gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates) Requires: libreport >= 2.0.9-5.el6_3.2 Removing: libreport-2.0.9-5.el6.centos.x86_64 (@base) libreport = 2.0.9-5.el6.centos Updated By: libreport-2.0.9-5.el6.centos.2.x86_64 (updates) libreport = 2.0.9-5.el6.centos.2 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Is the new libreport incorrectly named libreport-2.0.9-5.el6.centos.2.x86_64 instead of: libreport-2.0.9-5.el6.2.x86_64 or is the dependency of abrt incorrect? Mogens -- Mogens Kjaer, m...@lemo.dk http://www.lemo.dk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] skype not starting anymore, prelink issue?
On Wednesday 30 January 2013, wwp wrote: > I was running skype 4.1.0.20 on my 64-bit laptop for weeks (installed > in /opt, from an official skype binary archive, plus few 32-bit stuff > to get it working), when suddenly it stopped working, no way to start > it: How did you get Skype 4.1 to work on CentOS 6 x64_64? Yves -- Yves Bellefeuille "Simply put, E=mc^2 is liberal claptrap." -- Conservapedia.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
On 01/31/2013 12:37 PM, Johnny Hughes wrote: > On 01/31/2013 11:05 AM, Connie Sieh wrote: >> On Thu, 31 Jan 2013, Robert Moskowitz wrote: >> >>> On 01/31/2013 11:36 AM, John Doe wrote: From: Robert Moskowitz > I want to get the original version of /etc/clamd.d/amavis.conf from the > amavisd-new rpm to get the defaults to submit a bug report. I could not > figure out how to do this, so I did a reinstall, but it did not replace > this file (whatprovides says it comes from this rpm). > Is there a way to extract just the one file, and better yet, place it > elsewhere than its regular destination? You could also just have renamed your conf file temporarily, reinstalled, moved the default conf file and renamed back your conf file... >>> OK. I am set for what I needed. I went to the repo via http and >>> downloaded the rpm. I then used archive manager via nautilus to get to >>> the file(s) I needed. Now to write up the bug report. Minor item, but >>> it bugs me ;) >>> >> The command line way of getting 1 file out of a rpm is to rpm2cpio. >> >> rpm2cpio > >> >> Now you have a cpio archive which you can use to get files out of. > Or: > > rpm2cpio | cpio -idv > > That will extract all the files to the current directory (create a > temporarily directory and cd into it before you start). thanks eveyone for all these tips. I REALLY need to put together a couple of remember how to do it notes. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
On 01/31/2013 11:40 AM, Reindl Harald wrote: > > Am 31.01.2013 16:55, schrieb Robert Moskowitz: >> I want to get the original version of /etc/clamd.d/amavis.conf from the >> amavisd-new rpm to get the defaults to submit a bug report. I could not >> figure out how to do this, so I did a reinstall, but it did not replace >> this file (whatprovides says it comes from this rpm). >> >> Is there a way to extract just the one file, and better yet, place it >> elsewhere than its regular destination? > seems you are very new in the rpm world Actually very old to it. I use to do this stuff 10 years ago and my brain just ain't what it use to be. Use to do my own builds for a number of apps, but doubt I could do a build now! > > THANKFULLY a reinstall does not touch modified config-files > BUT you get a warning from yum that whatever.conf was installed > as watever.conf.rpmnew > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
On 01/31/2013 11:05 AM, Connie Sieh wrote: > On Thu, 31 Jan 2013, Robert Moskowitz wrote: > >> On 01/31/2013 11:36 AM, John Doe wrote: >>> From: Robert Moskowitz >>> I want to get the original version of /etc/clamd.d/amavis.conf from the amavisd-new rpm to get the defaults to submit a bug report. I could not figure out how to do this, so I did a reinstall, but it did not replace this file (whatprovides says it comes from this rpm). Is there a way to extract just the one file, and better yet, place it elsewhere than its regular destination? >>> You could also just have renamed your conf file temporarily, >>> reinstalled, moved the default conf file and renamed back >>> your conf file... >> OK. I am set for what I needed. I went to the repo via http and >> downloaded the rpm. I then used archive manager via nautilus to get to >> the file(s) I needed. Now to write up the bug report. Minor item, but >> it bugs me ;) >> > The command line way of getting 1 file out of a rpm is to rpm2cpio. > > rpm2cpio > > > Now you have a cpio archive which you can use to get files out of. Or: rpm2cpio | cpio -idv That will extract all the files to the current directory (create a temporarily directory and cd into it before you start). signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
On Thu, 31 Jan 2013, Robert Moskowitz wrote: > > On 01/31/2013 11:36 AM, John Doe wrote: >> From: Robert Moskowitz >> >>> I want to get the original version of /etc/clamd.d/amavis.conf from the >>> amavisd-new rpm to get the defaults to submit a bug report. I could not >>> figure out how to do this, so I did a reinstall, but it did not replace >>> this file (whatprovides says it comes from this rpm). >>> Is there a way to extract just the one file, and better yet, place it >>> elsewhere than its regular destination? >> You could also just have renamed your conf file temporarily, >> reinstalled, moved the default conf file and renamed back >> your conf file... > > OK. I am set for what I needed. I went to the repo via http and > downloaded the rpm. I then used archive manager via nautilus to get to > the file(s) I needed. Now to write up the bug report. Minor item, but > it bugs me ;) > The command line way of getting 1 file out of a rpm is to rpm2cpio. rpm2cpio > Now you have a cpio archive which you can use to get files out of. -Connie Sieh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] ACL/permissions question
Hello listmates, If I have a regular, ACL-capable filesystem on Linux (say, ext4 or xfs) is there a way for me to establish the following: 1) There is a directory, say, /home/joe . It is owned by user joe . No one but joe (and root, of course) can read or write anything in this directory. 2) No one can change permissions on that directory, not even joe. In other words, in joe all of a sudden joe decided to open his directory up to the world (or the group he is a member of) by doing something akin to: chmod 777 /home/joe he would not succeed. Thanks in advance for any help. Boris. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
On 01/31/2013 11:36 AM, John Doe wrote: > From: Robert Moskowitz > >> I want to get the original version of /etc/clamd.d/amavis.conf from the >> amavisd-new rpm to get the defaults to submit a bug report. I could not >> figure out how to do this, so I did a reinstall, but it did not replace >> this file (whatprovides says it comes from this rpm). >> Is there a way to extract just the one file, and better yet, place it >> elsewhere than its regular destination? > You could also just have renamed your conf file temporarily, > reinstalled, moved the default conf file and renamed back > your conf file... OK. I am set for what I needed. I went to the repo via http and downloaded the rpm. I then used archive manager via nautilus to get to the file(s) I needed. Now to write up the bug report. Minor item, but it bugs me ;) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
From: Robert Moskowitz > I want to get the original version of /etc/clamd.d/amavis.conf from the > amavisd-new rpm to get the defaults to submit a bug report. I could not > figure out how to do this, so I did a reinstall, but it did not replace > this file (whatprovides says it comes from this rpm). > Is there a way to extract just the one file, and better yet, place it > elsewhere than its regular destination? You could also just have renamed your conf file temporarily, reinstalled, moved the default conf file and renamed back your conf file... JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
On 01/31/2013 11:01 AM, m.r...@5-cent.us wrote: > Robert Moskowitz wrote: >> I want to get the original version of /etc/clamd.d/amavis.conf from the >> amavisd-new rpm to get the defaults to submit a bug report. I could not >> figure out how to do this, so I did a reinstall, but it did not replace >> this file (whatprovides says it comes from this rpm). >> >> Is there a way to extract just the one file, and better yet, place it >> elsewhere than its regular destination? > Didn't it create it in the normal destination as amavis.conf.rpmnew? No it did not. I am thinking I had the current file open in gedit and MAYBE that had a bearing on the reinstall? I will attempt to download just the rpm and try to open it with archive manager. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to extract one file from rpm using yum?
Robert Moskowitz wrote: > I want to get the original version of /etc/clamd.d/amavis.conf from the > amavisd-new rpm to get the defaults to submit a bug report. I could not > figure out how to do this, so I did a reinstall, but it did not replace > this file (whatprovides says it comes from this rpm). > > Is there a way to extract just the one file, and better yet, place it > elsewhere than its regular destination? Didn't it create it in the normal destination as amavis.conf.rpmnew? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Antwort: How to extract one file from rpm using yum?
centos-boun...@centos.org wrote on 31.01.2013 16:55:37: > Robert Moskowitz > Gesendet von: centos-boun...@centos.org > > 31.01.2013 16:55 > > Bitte antworten an > CentOS mailing list > > An > > CentOS mailing list > > Kopie > > Thema > > [CentOS] How to extract one file from rpm using yum? > > I want to get the original version of /etc/clamd.d/amavis.conf from the > amavisd-new rpm to get the defaults to submit a bug report. I could not > figure out how to do this, so I did a reinstall, but it did not replace > this file (whatprovides says it comes from this rpm). > > Is there a way to extract just the one file, and better yet, place it > elsewhere than its regular destination? > > thanks > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos Hi Robert, you can extract this file with cpio or open it with mc like a archive (zip, tar, ...) Mit freundlichen Grüßen Andreas Reschke Unix/Linux-Administration andreas.resc...@behrgroup.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] How to extract one file from rpm using yum?
I want to get the original version of /etc/clamd.d/amavis.conf from the amavisd-new rpm to get the defaults to submit a bug report. I could not figure out how to do this, so I did a reinstall, but it did not replace this file (whatprovides says it comes from this rpm). Is there a way to extract just the one file, and better yet, place it elsewhere than its regular destination? thanks ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixed - Re: More on amavis/clam permission errors on Centos 6.3
On 01/31/2013 09:26 AM, Nicolas Thierry-Mieg wrote: > Robert Moskowitz wrote: >>> As you have seen there are differences between the packages. This makes >>> the CentOS documentation worthless to you as you are not using the same >>> versions used in the documentation. >> I had hopes that the 'official' packaging would work well, particularly >> now that both are on the same release. I really wanted to do this all >> 'official' packages. I know there is nothing wrong with rpmforge, I use >> it for a number of things, just this time around for mail, I was >> shooting for 'fully supported cruft'. Shows how good that approach takes! > I'm not sure what made you think so, Oh, I don't know. Maybe that it is run under the Fedora/Redhat umbrella as a recognized SIG? :) > but epel is no more "official" than > rpmforge. It's just another third party repo. > The only "official" repos are base and updates. Perhaps CR could qualify > as semi-official... and that's it, I'ld say. > > glad Ned could help you solve your problem. I have submitted a bug report on this: 906396 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixed - Re: More on amavis/clam permission errors on Centos 6.3
Robert Moskowitz wrote: > >> As you have seen there are differences between the packages. This makes >> the CentOS documentation worthless to you as you are not using the same >> versions used in the documentation. > > I had hopes that the 'official' packaging would work well, particularly > now that both are on the same release. I really wanted to do this all > 'official' packages. I know there is nothing wrong with rpmforge, I use > it for a number of things, just this time around for mail, I was > shooting for 'fully supported cruft'. Shows how good that approach takes! I'm not sure what made you think so, but epel is no more "official" than rpmforge. It's just another third party repo. The only "official" repos are base and updates. Perhaps CR could qualify as semi-official... and that's it, I'ld say. glad Ned could help you solve your problem. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Fixed - Re: More on amavis/clam permission errors on Centos 6.3
On 01/31/2013 07:05 AM, Ned Slider wrote: > On 31/01/13 11:17, Robert Moskowitz wrote: >> On 01/31/2013 02:30 AM, John Hinton wrote: >>> On 1/30/2013 5:05 PM, Robert Moskowitz wrote: On 01/30/2013 04:31 PM, Nicolas Thierry-Mieg wrote: > Robert Moskowitz wrote: >> I should probably find either the amavis or clam list(s) and take this >> there? >> > >> Oh, I have not applied the updated policy rpms that Dan Walsh pointed me >> to. This is all 'out of the box' rpms, following the amavis/clamav >> recommendations from: http://wiki.centos.org/HowTos/Amavisd > is it? so your rpms come from rpmforge? I thought you mentioned epel at > some point. Hopefully you're not mixing them? Sorry, I followed the HowTo, but got all the rpms from epel. > If you are, then that might be your problem. > If you really followed the wiki instructions you must be using RF > packages, so you could take it to the RF list. > And if you're using epel, then you didn't follow the wiki instructions > but nevertheless you should take it to the epel list... epel list. Hmm. Now to find that. Thanks for the direction. >>> Read near the top of the amavis config file. It will reference the >>> directories you are having trouble with. It tells you to create them and >>> that they need to be owned by whatever you set the amavis user to be. It >>> is all right there in the conf file. >>> >> Yes, I read that. >> >> >> amavis from the epel repo defaults to /var/spool/amavisd which is owned >> by amavis:amavis with permissions 700. >> >> The rpm created the subdirs under this of quarantine, tmp, and db also >> owned by amavis:amavis with permissions 700. I had to create var myself >> for spamassassin to use. >> >> The permissions problem is under /var/spool/amavis/tmp if you look at >> the maillog entry. I have altered all permissions to 750 and still have >> the problem; the directory created is with 700, and perhaps that is why >> the problem? >> > Permissions should be 750 as the clamav user is a member of the amavis > group and needs group access. So this is one bug for epel, as the rpm creates the directories with the wrong permissions. Either do it right, or leave to the installer. So I just changed all the amavis directories to 750 and restarted both amavisd and clamd and it worked this time! I thought I did the restart back before the rebuild, but maybe I didn't or I had other things configured wrong. So this IS a bug in the packaging for me to submit to epel. > >> I am thinking to change the clamd conf files to run with user amavis >> instead of clam and see if that gets around the problem... >> > That will likely cause other problems. The clamav user just needs to be > a member of the amavis group. That was my initial read, but as my frustration was rising, it looked like a way to troubleshoot the problem. So now I don't have to try this. > >> I have joined the epel-devel list (I did not find an epel-users list) >> and posted this there yesterday. I see that epel repo is the same >> version currently available from rpmforge that the howto uses. >> Interestingly, rpmforge uses userid clamav and epel uses userid clam. >> Don't know what other differences there are. So far no replies on the >> epel list. >> > As you have seen there are differences between the packages. This makes > the CentOS documentation worthless to you as you are not using the same > versions used in the documentation. I had hopes that the 'official' packaging would work well, particularly now that both are on the same release. I really wanted to do this all 'official' packages. I know there is nothing wrong with rpmforge, I use it for a number of things, just this time around for mail, I was shooting for 'fully supported cruft'. Shows how good that approach takes! > You should take this thread, and your issue, to the EPEL list as it > really has nothing to do with CentOS. Well I have and will post this there as well and submit the bug report. I have two on these packages so far. I started here as I did not know where best to take it (for example an amavis or clamav list?) but more becuase I was hoping that there would be Centos users that have worked with these packages and might be kind enough to share their insights. And thank you for your help. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 - which repos to use?
On Thu, Jan 31, 2013 at 1:03 AM, Bry8 Star wrote: > When using multiple repo, then how would i know, an > app/lib from non-CentOS (that is, 3rd party repo) is going > to conflict or not with CentOS core, base, essential > app/lib packages ? > I don't think there is any way to know that. And more to the point, using any single 3rd party repo is likely to work at least until the next update because the contents will have been tested against the base distro - as long as the packages are intended for use with RHEL/Centos. The harder problem is that when you use multiple 3rd party repos you can have packages with the same names and leapfrogging version numbers but that are built or configured differently. So you install from one repo but it appears later with a higher version number in a different one that you have enabled and is replaced by something you don't expect. This may cause dependency issues in the yum update or sometimes just as bad, update without errors but fail to work because of build or configuration differences. I've always thought it would be helpful if yum notified you whenever it was about to overwrite an existing package with one from a different repo, but even that might not be enough. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] More on amavis/clam permission errors on Centos 6.3
On 31/01/13 11:17, Robert Moskowitz wrote: > > On 01/31/2013 02:30 AM, John Hinton wrote: >> On 1/30/2013 5:05 PM, Robert Moskowitz wrote: >>> On 01/30/2013 04:31 PM, Nicolas Thierry-Mieg wrote: Robert Moskowitz wrote: > I should probably find either the amavis or clam list(s) and take this > there? > > Oh, I have not applied the updated policy rpms that Dan Walsh pointed me > to. This is all 'out of the box' rpms, following the amavis/clamav > recommendations from: http://wiki.centos.org/HowTos/Amavisd is it? so your rpms come from rpmforge? I thought you mentioned epel at some point. Hopefully you're not mixing them? >>> Sorry, I followed the HowTo, but got all the rpms from epel. >>> If you are, then that might be your problem. If you really followed the wiki instructions you must be using RF packages, so you could take it to the RF list. And if you're using epel, then you didn't follow the wiki instructions but nevertheless you should take it to the epel list... >>> epel list. Hmm. Now to find that. >>> >>> Thanks for the direction. >>> >> Read near the top of the amavis config file. It will reference the >> directories you are having trouble with. It tells you to create them and >> that they need to be owned by whatever you set the amavis user to be. It >> is all right there in the conf file. >> > Yes, I read that. > > > amavis from the epel repo defaults to /var/spool/amavisd which is owned > by amavis:amavis with permissions 700. > > The rpm created the subdirs under this of quarantine, tmp, and db also > owned by amavis:amavis with permissions 700. I had to create var myself > for spamassassin to use. > > The permissions problem is under /var/spool/amavis/tmp if you look at > the maillog entry. I have altered all permissions to 750 and still have > the problem; the directory created is with 700, and perhaps that is why > the problem? > Permissions should be 750 as the clamav user is a member of the amavis group and needs group access. > I am thinking to change the clamd conf files to run with user amavis > instead of clam and see if that gets around the problem... > That will likely cause other problems. The clamav user just needs to be a member of the amavis group. > I have joined the epel-devel list (I did not find an epel-users list) > and posted this there yesterday. I see that epel repo is the same > version currently available from rpmforge that the howto uses. > Interestingly, rpmforge uses userid clamav and epel uses userid clam. > Don't know what other differences there are. So far no replies on the > epel list. > As you have seen there are differences between the packages. This makes the CentOS documentation worthless to you as you are not using the same versions used in the documentation. You should take this thread, and your issue, to the EPEL list as it really has nothing to do with CentOS. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anything Like Solaris' Live Upgrade?
On 01/29/2013 02:03 PM, Tim Evans wrote: > Thanks to everyone for their replies. Excellent discussion, Tim. Thanks for bringing this up and coming back with such good arguments. Some of the objections I've seen on this thread: 1. LiveUpgrade takes too much CPU and disk space. Not if your system is sized appropriately. Simple recovery procedures are worth considerable effort and expense, which is why these features exist in Solaris. Redhat and Fedora aren't quite there yet. But at least people are talking about it here. 2. YUM and various combinations of LVM are faster? The goal isn't to make the overall implementation process faster, although it's been reasonable on most major upgrades to Solaris. The important thing is to make the reboot and resumption of services faster, including back-out. A major upgrade will require a reboot in any case. If you're just doing a minor patch not requiring changes to running processes, you can always use LiveUpgrade to test it out without impacting your running system. 3. There's a Solaris mindset that makes people prefer LiveUpgrade? Not so. AIX and some versions of SVR4 have had ABE support (Teradata comes to mind). I think AIX lets you upgrade running processes in some cases. TMOS with F5 has it. Networking gear often has the ability to upgrade a target volume and rapidly boot off it with the ability to boot back. LiveUpgrade in Solaris is just an implementation of offline upgrading/maintenance. I see several techniques on this thread with potential to make offline maintenance possible in the near future, or obtain a useful alternative (pardon the pun). It seems to me that if YUM, RHN, and RPM were designed to work in an alternate root, we'd be 90% done with the project of implementing offline maintenance for Redhat/Fedora. If yum upgrade --root=/a would work, GRUB and /etc/fstab changes could readily be automated with existing tools. I hope this discussion stays active in Linux circles. Steve ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] More on amavis/clam permission errors on Centos 6.3
On 01/31/2013 02:30 AM, John Hinton wrote: > On 1/30/2013 5:05 PM, Robert Moskowitz wrote: >> On 01/30/2013 04:31 PM, Nicolas Thierry-Mieg wrote: >>> Robert Moskowitz wrote: I should probably find either the amavis or clam list(s) and take this there? >>> Oh, I have not applied the updated policy rpms that Dan Walsh pointed me to. This is all 'out of the box' rpms, following the amavis/clamav recommendations from: http://wiki.centos.org/HowTos/Amavisd >>> is it? so your rpms come from rpmforge? I thought you mentioned epel at >>> some point. Hopefully you're not mixing them? >> Sorry, I followed the HowTo, but got all the rpms from epel. >> >>> If you are, then that might be your problem. >>> If you really followed the wiki instructions you must be using RF >>> packages, so you could take it to the RF list. >>> And if you're using epel, then you didn't follow the wiki instructions >>> but nevertheless you should take it to the epel list... >> epel list. Hmm. Now to find that. >> >> Thanks for the direction. >> > Read near the top of the amavis config file. It will reference the > directories you are having trouble with. It tells you to create them and > that they need to be owned by whatever you set the amavis user to be. It > is all right there in the conf file. > Yes, I read that. amavis from the epel repo defaults to /var/spool/amavisd which is owned by amavis:amavis with permissions 700. The rpm created the subdirs under this of quarantine, tmp, and db also owned by amavis:amavis with permissions 700. I had to create var myself for spamassassin to use. The permissions problem is under /var/spool/amavis/tmp if you look at the maillog entry. I have altered all permissions to 750 and still have the problem; the directory created is with 700, and perhaps that is why the problem? I am thinking to change the clamd conf files to run with user amavis instead of clam and see if that gets around the problem... I have joined the epel-devel list (I did not find an epel-users list) and posted this there yesterday. I see that epel repo is the same version currently available from rpmforge that the howto uses. Interestingly, rpmforge uses userid clamav and epel uses userid clam. Don't know what other differences there are. So far no replies on the epel list. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2way authentication for SSH?
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Rudi Ahlers Sent: Monday, January 28, 2013 8:52 AM To: CentOS Subject: [CentOS] 2way authentication for SSH? Hi, Does anyone know of a stable / working "2way authentication" system for SSH, and even web authentication services? Most of the banks in South Africa have a system that, when you want to make a payment, they send you an SMS and you need to verify the action with a secret code which was SMS'd to you. gmail also has this. Does anyone know of a "universal" plugin / application that can be used with SSH and even websites like Wordpress / Joolma / Webmin / etc? Any pointer would be appreciated. -Original Message- Is it really 2way (as in mutual) authentication or 2factor authentication? Mutual authentication is normally done with ssl (server + client) certificates. Most http engines (apache, tomcat) do support them. For two factor (have, know) authentication "some assembly" is required, at least for openssh. See: http://roumenpetrov.info/openssh/ Generally speaking, you _do_ want a trusted third party (like a CA) and certainly _not_ another additional unreliable man-in-the-middle. I mean: like google. But should I trust them with regards to security and availability??? HW __ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
