Discuss

discuss@lists.centos.org

34758 discussions

CentOS-announce Digest, Vol 41, Issue 5
by centos-announce-request＠centos.org 10 Jul '08

10 Jul '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Re: Bind Patch (Karanbir Singh) 2. CESA-2008:0533 Important CentOS 3 ia64 bind - security update (Pasi Pirhonen) 3. CESA-2008:0533 Important CentOS 3 s390(x) bind - security update (Pasi Pirhonen) 4. CESA-2008:0533 Important CentOS 4 ia64 bind - security update (Pasi Pirhonen) 5. CESA-2008:0533 Important CentOS 4 s390(x) bind - security update (Pasi Pirhonen) 6. CESA-2008:0584 Important CentOS 3 ia64 pidgin - security update (Pasi Pirhonen) 7. CESA-2008:0584 Important CentOS 4 ia64 pidgin - security update (Pasi Pirhonen) 8. CESA-2008:0583 Important CentOS 4 ia64 openldap - security update (Pasi Pirhonen) 9. CESA-2008:0584 Important CentOS 3 s390(x) pidgin - security update (Pasi Pirhonen) 10. CESA-2008:0584 Important CentOS 4 s390(x) pidgin - security update (Pasi Pirhonen) 11. CESA-2008:0583 Important CentOS 4 s390(x) openldap - security update (Pasi Pirhonen) 12. CESA-2008:0584 Important CentOS 5 i386 pidgin Update (Karanbir Singh) 13. CESA-2008:0584 Important CentOS 5 x86_64 pidgin Update (Karanbir Singh) 14. CESA-2008:0583 Important CentOS 5 i386 openldap Update (Karanbir Singh) 15. CESA-2008:0583 Important CentOS 5 x86_64 openldap Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 09 Jul 2008 13:06:16 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] Re: Bind Patch To: Edward Casteloes <Edward.Casteloes(a)esendex.com> Cc: centos-announce(a)centos.org Message-ID: <4874A9B8.7020805(a)centos.org> Content-Type: text/plain; charset=UTF-8; format=flowed read the announcement posted and the check the url in there. Edward Casteloes wrote: > > > Hi, > > I have seen that the 9.3.4 bind patch is available for Centos 5, does > this patch rectify the big DNS issue that was just announced yesterday? > The reason I ask is according to ISC they recommend updating to 9.3.5-P1 > http://www.isc.org/index.pl?/sw/bind/forgery-resilience.php . I am sure > you are getting a lot of mail about this, but if you could advise it > would be appreciated. > > Many Thanks, > > Ed > > > *Edward Casteloes* > Operations Manager > Esendex Ltd > > T: +44 (0)115 852 5774 > F: +44 (0)115 852 5757 > Email: Edward.Casteloes(a)esendex.com <mailto:Edward.Casteloes@esendex.com> > Web: www.esendex.com <http://www.esendex.com/> > > Esendex: Every Message Matters > > *Confidentiality*: This e-mail (and any associated files) is intended > only for the use of kbsingh(a)centos.org, centos-announce(a)centos.org and > may contain information that is confidential, subject to copyright or > constitutes a trade secret. If you are not kbsingh(a)centos.org, > centos-announce(a)centos.org you are hereby notified that any disclosure, > copying or distribution of this message, or files associated with this > message, is strictly prohibited. If you have received this message in > error, please notify us immediately by replying to the message and then > delete it from your computer. Messages sent to and from us may be > monitored. The views expressed in this message are those of the author > Edward Casteloes and do not necessarily represent the views of Esendex Ltd. > ** > *Security*: This e-mail and any attachments are believed to be free from > any virus but it is the responsibility of the recipient to ensure this > is so. E-mail is not a 100% secure communications medium. We recommend > you observe this when e-mailing us. > *Esendex Ltd* is a limited company registered in the UK, with company > number 04217280 and having its registered office at 32a Stoney Street • > Nottingham • NG1 1LL • United Kingdom. > [v1.1 EN] ------------------------------ Message: 2 Date: Wed, 9 Jul 2008 18:32:38 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 3 ia64 bind - security update To: centos-announce(a)centos.org Message-ID: <20080709153238.GC31936(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2008:0533 https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/bind-9.2.4-22.el3.ia64.rpm updates/ia64/RPMS/bind-chroot-9.2.4-22.el3.ia64.rpm updates/ia64/RPMS/bind-devel-9.2.4-22.el3.ia64.rpm updates/ia64/RPMS/bind-libs-9.2.4-22.el3.ia64.rpm updates/ia64/RPMS/bind-utils-9.2.4-22.el3.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

yum dependency problem
by fred smith 10 Jul '08

10 Jul '08

Hi: Today when I do yum update I get this: Resolving Dependencies --> Running transaction check --> Processing Dependency: libdirectfb-0.9.so.25 for package: mplayer ---> Package directfb.i386 0:1.0.1-1.el5.rf set to be updated ---> Package amrnb.i386 0:7.0.0.2-1.el5.rf set to be updated ---> Package gsm.i386 0:1.0.12-1.el5.rf set to be updated --> Finished Dependency Resolution Error: Missing Dependency: libdirectfb-0.9.so.25 is needed by package mplayer and I have to admit I don't understand that.... it says it's going to update directfb.i386 then it says directfb is required by mplayer. Huh? perhaps it means it's trying to replace my existing directfb with a DIFFERENT verson and can't because mplayer needs the existing one? the existing directfb I have is: directfb-0.9.25.1-1.el5.rf which came from the same repo as my mplayer: mplayer-1.0-0.38.rc1try2.el5.rf so am I to assume that some other repo (with a greater priority, since I'm using the priority plugin) is trying to overwrite the one I got from the rf repo? the base repos (base, updates, addons and extras) are all priority 1, centosplus and contrib are 2. rpmforge is 10. that's all there are. What's wrong here? Thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

3 3

Mysql replication stopped after 5.2 update.
by Alessandro Ren 10 Jul '08

10 Jul '08

2 3

Re: [CentOS] Shell Script Question
by Les Bell 10 Jul '08

10 Jul '08

"Joseph L. Casale" <JCasale(a)activenetwerx.com> wrote: >> What's the simplest way to increment the number 0000 up by one until some other 4 digit number while preserving leading zero's until the 1000's has a digit other than 0? << Easy: $ seq -f %04g 0000 9999 Best, --- Les Bell, RHCE, CISSP [http://www.lesbell.com.au] Tel: +61 2 9451 1144 FreeWorldDialup: 800909

1 0

Shell Script Question
by Joseph L. Casale 10 Jul '08

10 Jul '08

What's the simplest way to increment the number 0000 up by one until some other 4 digit number while preserving leading zero's until the 1000's has a digit other than 0? Thanks! jlc

4 4

Total lockup caused by Shift-{print screen}
by Robert Nichols 10 Jul '08

10 Jul '08

I just had the misfortune to press Shift-{print screen} accidentally while in a Gnome desktop, and the result was a completely unresponsive system where the only recovery was a power switch initiated shutdown. Further investigation shows the runaway creation of gnome-screenshot processes. System is CentOS 5.2 fully updated on an Intel i686. Suggestions about what component should receive the bugzilla report are welcome. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.

2 3

CentOS 5.2 kernel [2.6.18-92.1.1.el5] crashes on dual-PIII Compaq ProLiant 3000
by Wojtek Pilorz 09 Jul '08

09 Jul '08

After yum upgrade, the new CentOS5 kernel [ kernel-2.6.18-92.1.1.el5.i686 ] crashes each time early in boot process on Compaq ProLiant 3000 with dual Pentium3 CPU (600 MHz, CPU0: Intel Pentium III (Katmai) stepping 03, CPU1 the same). I get kernel panic at powernowk8_init+0x05e/0x1c3. The previous kernel [ kernel-2.6.18-53.1.21.el5.i686 ] seems to work fine. I am wondering if anyone has met this on PIII CPU ? I have found 99.9% identical problem on http://www.nabble.com/net-5501-and-RHEL5.2-td18024549.html (only esp and task slightly different from what I have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU. On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem. Is it normal, that powernowk8_init gets called on PIII CPU? Best regards, Wojtek

13 18

Flaky desktop audio behavior.
by William L. Maltby 09 Jul '08

09 Jul '08

Might have some kind of bug here. I want to know if anybody else is seeing this. It's happened twice now, so I should be able to repeat it. $ rpm -q centos-release centos-release-5-2.el5.centos On my desktop, I "su -" to another user. Then "nohup thunderbird", it gets the mail and plays the announcement. ISTM this is an error right off the bat as this user is not the desktop owner. But that's not the main point. I really am OK with that behavior in my instance. The problem is that the sound system goes muted, as indicated by the volume control on my desktop panel and I can't recover from it except by a reboot. When I try to open the sound control panel, I get an error panel saying "No volume control GStreamer plugins and/or devices found". If I just try to un-mute, there's no error message but the status does not change. I've attached a snapshot of the error panel. Further, in chasing another problem that Jim (hce) had, we have done this: # find . -type f -exec echo {} \; -exec cat {} \; >/tmp/asound.play.bug Normally it acts as expected but now I get this. cat: ./acpi/event: Device or resource busy cat: ./sys/net/ipv6/route/flush: Operation not permitted cat: ./sys/net/ipv4/route/flush: Operation not permitted cat: ./sys/fs/binfmt_misc/register: Invalid argument cat: ./sysrq-trigger: Invalid argument and it hangs right there. <Ctl>-<C> breaks OK. I feel it might be related to Jim's problem. I feel it might be a bug. Can anybody reproduce? I think the T'bird step is coincidental. I think any sound played as another user should reproduce it. Hmmm ... I might be assuming to much if I assume another user is significant. TIA -- Bill

2 10

Need basic PPPoE startup help
by Robert Moskowitz 09 Jul '08

09 Jul '08

I need basic PPPoE startup help. adsl-start DID bring up my PPPoE link (ppp0) to my ISP over eth0 via the DSL modem/bridge. My IPv4 CIDR block is routing and Shorewall is doing the firewalling. But shorewall has to be started after ppp0 is up and working. For now this means running shorewall restart (or start?). Shorewall 4.2 will have a way to restart shorewall without recompiling, I learned on the their list. In /etc/sysconfig/network-scripts/ifcfg-ppp0 I have: BOOTPROTO=dialup NAME=DSLppp0 DEVICE=ppp0 TYPE=xDSL ONBOOT=no Should ONBOOT be changed to yes, or is there some startup script that I should add the /sbin/adsl-start ppp0 command line followed with the shorewall restart command? I am away at IEEE 802 plenary meeting next week, and I need this to be automated in case of system glitches. Also sometimes the Speedstream just stops forwarding datagrams. Supposedly if it overheats. This requires a power recycle for the speedstream (and my ISP will not use anything else for the modem services). I suspect this will glich the PPPoE connection as well, so I will need some sort of watchdog and a restart of ppp0 and Shorewall. Attached is a rather large script of a user that I picked up on the Shorewall list for some Linux distro. I am NOT a script reader, let alone writer. Should I use this (how would I modify it for Centos and a ppp0 interface) and where would I place it to run as needed? ======================================================= #!/usr/bin/perl -w #THIS SCRIPT CREATED BY EJM (alias Erik Mundall) IN ORDER TO MAINTAIN A CONSTANT CONNECTION WITH THE TWO #PPPOE ADSL LINES WHICH HAVE PROVEN TO BE UNRELIABLE/UNSTABLE. 15 APRIL 2008 # #THIS PROGRAM NEEDS TO FOLLOW THE FOLLOWING ROUTINE IN ORDER TO MAINTAIN CONNECTIVITY OF THE TWO PPPOE LINES #AND TO SHARE THE INTERNET LOAD ACROSS THOSE AND ACROSS THE STATIC LINE # #THE STATIC SHOULD NEVER FAIL. THIS SCRIPT IS INTENDED TO ADDRESS ONLY THE INSTABILITY OF THE TWO PPPOE #LINES, AND WILL DO NOTHING FOR THE STATIC LINE IF IT SHOULD FAIL. # # #STEP ONE: THE PROGRAM SHOULD IDENTIFY THE LINE(S) THAT ARE DOWN, IF ANY, AND ISOLATE THEM. #STEP TWO: THE PROGRAM SHOULD RECONFIGURE AND RESTART SHOREWALL TO MATCH THE LINES THAT ARE UP. #STEP THREE: THE PROGRAM SHOULD FOCUS ON RESTORING THE DROPPED PPPOE LINE(S). #STEP FOUR: THE PROGRAM MUST REPEAT STEP TWO ONCE STEP THREE HAS SUCCEEDED. ############################################### # REQUIRED VARIABLES. THESE MUST BE SET PROPERLY!!! our $admin_email =q`your_email_address(a)your_domain_name.com`; our $domain_name = "your_domain_name.com"; our $GATEWAY_1 = 'x.x.x.x'; #GATEWAY OF PPP0 LINE our $GATEWAY_2 = 'x.x.x.x'; #GATEWAY OF PPP1 LINE our $IPADDRESS_1 = 'x.x.x.x'; #STATIC IP ADDRESS OF PPP0 LINE (ASSIGNED BY ISP) our $IPADDRESS_2 = 'x.x.x.x'; #STATIC IP ADDRESS OF PPP1 LINE (ASSIGNED BY ISP) our $DEBUG=1; #SET THIS TO 1 FOR DEBUGGING, 0 TO TURN DEBUGGING OFF our $DEBFILE='/var/log/ppp/debug.log'; #THE /var/log/ppp DIRECTORY MUST EXIST FOR THE DEBUG FILE our $logfile='/var/log/ppp/maint.log'; #THE /var/log/ppp DIRECTORY MUST EXIST FOR LOGGING. ############################################### # BELOW THIS LINE, NOTHING MORE SHOULD NEED TO BE CONFIGURED. our @ifconf = (); our @iprout = `/sbin/ip route`; our $p1; our $p2; our $ppp0=0; our $ppp1=0; our $FAILED='FALSE'; our $FAIL='TRUE'; our $attempt=0; our $date=''; our @data=(); our @updata=(); our @log=(); our @total_log=(); our $cur_day=0; our $cur_month=0; our $cur_year=0; our $late_day=0; our $late_month=0; our $late_year=0; our %months=(Jan,1,Feb,2,Mar,3,Apr,4,May,5,Jun,6,Jul,7,Aug,8,Sep,9,Oct,10,Nov,11,Dec,12); our $start_time=`/bin/date`; our $stop_time; ############################################# ### SAFEGUARD AGAINST MULTIPLE PROCESSES! ### ############################################# our @pslist = `/bin/ps auxw`; our $line=''; our $scripts=0; foreach $line(@pslist) { if ($line=~s/(ppp-line-maintenance\.pl)/$1/) { #THIS SCRIPT MUST NOT BE RENAMED, OR IF IT IS, THIS LINE MUST BE ADJUSTED ACCORDINGLY!!!! $scripts++; if ($DEBUG==1) {print "Line:$line\nScripts:$scripts\n" }; }; }; if ($scripts<=2) { #CONTINUE THIS SCRIPT IF ONLY ONE OCCURRENCE (THIS ONE) OF THIS SCRIPT IN CURRENT PROCESS LIST ############# ### BEGIN ### ############# if ($DEBUG==1) {open DLOG, ">$DEBFILE" or die "Cannot open debugging file!\n"}; &ping1; &ping2; &checkdowned; &trimlog; if ($DEBUG==1) {close DLOG}; } #END 'CONTINUE SCRIPT' sleep 2; exit; ###################################################################################################### ### SUBROUTINES ### ################### sub ping1 { $p1=`/bin/ping -c 3 $GATEWAY_1`; if ($p1=~s/100\%\spacket\sloss//) {$p1='DOWN'}; if ($p1=~s/unreachable//) {$p1='DOWN'}; if ($DEBUG==1) {print DLOG "p1:$p1\n"}; return $p1; }; sub ping2 { $p2=`/bin/ping -c 3 $GATEWAY_2`; if ($p2=~s/100\%\spacket\sloss//) {$p2='DOWN'}; if ($p2=~s/unreachable//) {$p2='DOWN'}; if ($DEBUG==1) {print DLOG "p2:$p2\n"}; return $p2; }; sub trimlog { ################ ### TRIM LOG ### ################ # THIS PRUNES THE LOG FILE TO JUST THE PREVIOUS THREE MONTH PERIOD. open DATA, "<$logfile" or die "Cannot read PPP maint log file!\n"; @data = <DATA>; close DATA; $date = `/bin/date`; #$cur_month = (Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov,Dec)[(localtime)[4]]; $cur_month = (localtime)[4]; $cur_year = (localtime)[5]; $cur_year+=1900; $cur_day = (localtime)[3]; #PPP Check: Wed Jan 30 09:20:01 CST 2008 [sample from log] foreach $line(@data) { if ($line=~m/PPP\sCheck:\s\w{3}\s(\w{3})\s(\d{2}).{14}(\d{4})/) { $late_month=$months{$1}; $late_day=$2; $late_year=$3; if ( ($late_year==$cur_year) && ( (($cur_month-$late_month)>=3) && ($late_day<=$cur_day) ) ) {@updata=()} elsif ( ($late_year<$cur_year) && ( (($late_month-$cur_month)<=9) && ($late_day<=$cur_day) ) ) {@updata=()} else { push @updata, $line } } else { push @updata, $line }; } open DATA, ">$logfile" or die "Cannot write PPP maint log file!\n"; print DATA @updata; close DATA; ################### END TRIM LOG }; ############################## ### Check for Downed Lines ### ############################## sub checkdowned { while ($FAIL eq 'TRUE') { @ifconf=(); @ifconf = `/sbin/ifconfig`; $FAIL='FALSE'; while (@ifconf) { $line=shift @ifconf; if ($line=~m/ppp0/) { if ($DEBUG==1) {print DLOG "PPPO:$ppp0 "}; $ppp0=1; if ($DEBUG==1) {print DLOG "PPPO:$ppp0 "}; $line=shift @ifconf; if ($line=~m/$IPADDRESS_1/) {$ppp0+=2}; if ($DEBUG==1) {print DLOG "PPPO:$ppp0 "}; $line=shift @ifconf; if ($line=~m/UP /) {$ppp0+=4}; if ($DEBUG==1) {print DLOG "PPPO:$ppp0\n"}; }; if ($line=~m/ppp1/) { if ($DEBUG==1) {print DLOG "PPP1:$ppp1 "}; $ppp1=1; if ($DEBUG==1) {print DLOG "PPP1:$ppp1 "}; $line=shift @ifconf; if ($line=~m/$IPADDRESS_2/) {$ppp1+=2}; if ($DEBUG==1) {print DLOG "PPP1:$ppp1 "}; $line=shift @ifconf; if ($line=~m/UP /) {$ppp1+=4}; if ($DEBUG==1) {print DLOG "PPP1:$ppp1\n"}; print $line }; } $attempt++; if ($DEBUG==1) {print "ATTEMPT: $attempt\n"}; if ($FAILED eq 'TRUE') {push @log, "Attempt#:$attempt > PPP0:$ppp0 PPP1:$ppp1\n"}; if ($ppp0<7) { if ($DEBUG==1) {print "$ppp0: Restarting ppp0 line by ifdown/ifup commands...\n"}; system("/sbin/ifdown ppp0"); sleep 3; system("/sbin/ifup ppp0"); }; if ($ppp1<7) { if ($DEBUG==1) {print "$ppp1: Restarting ppp1 line by ifdown/ifup commands...\n"}; system("/sbin/ifdown ppp1"); sleep 3; system("/sbin/ifup ppp1"); }; if ($FAILED eq 'TRUE') { push @log, `/bin/date`."\n"; push @log, @iprout."\n\n"; open LOG, ">>$logfile"; print LOG @log; close LOG; } push @total_log, @log; @log=(); my $testppp0=ping0; my $testppp1=ping1; if ($DEBUG==1) {print "testppp0: $testppp0 testppp1:$testppp1\n"}; if (($testppp0 eq 'DOWN') || ($testppp1 eq 'DOWN')) { $FAIL='TRUE' }; if ($FAIL eq 'TRUE') {$FAILED='TRUE'}; if ($DEBUG==1) {print DLOG "FAIL:$FAIL\n"}; if ($FAILED eq 'TRUE') { system("/etc/init.d/shorewall", "restart"); system("/etc/init.d/snmpd restart"); open LOG, ">>$logfile" or die "Cannot open PPP maint log file!\n"; print LOG @log; close LOG; push @total_log, @log; $stop_time=`/bin/date`; ######################################################################################################### #NOW, SEND AN EMAIL OR CAUSE AN ERROR SO THAT CRON WILL EMAIL THE SYSADMIN A NOTICE OF THIS NECESSITY!!! system("/bin/mail -t <<EOF To: $admin_email From: pppoe-maintenance\@$domain_name Subject: PPPoE Dropped Connection Restored!\n\n A PPPoE Connection was dropped or was lost. It should now be restored. The restoration of the line began at: $start_time -- and finished at -- $stop_time. Here is the log from this process: @total_log END OF REPORT. EOF "); ############################################################################################################ } else { open LOG, ">>$logfile" or die "Cannot open PPP maint log file!\n"; print LOG "PPP Check: ".`/bin/date`; close LOG; }; #END IF FAILED } #END WHILE FAIL print "SUCCEEDED AFTER $attempt ATTEMPTS!\n"; } #END SUB CHECKDOWNED

1 1

pm-utils - ATrpms updates a system package on the stable branch
by Kenneth Burgener 09 Jul '08

09 Jul '08

I performed a clean minimal CentOS 5.2 install, fully updated the system, and then added the ATrpms repository. When I perform an update after adding the ATrpms repository, the package pm-utils is updated the the ATrpms repository. My understanding is there should not have been any updates as the stable version does not update system packages, right? "The CentOS 5/RHEL 5 repository from atrpms.net is safe to use, if you only use the stable version. Packages in there do not overwrite system packages." [1] If this is true, why did this package get updated? Thanks, Kenneth [1] http://wiki.centos.org/AdditionalResources/Repositories/

10 20

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss