Discuss July 2008

discuss@lists.centos.org

347 participants
435 discussions

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

hard drive info
by Hiep Nguyen 09 Jul '08

09 Jul '08

i'm acessing a centos box via ssh, is there any way that i can find out the hard drive info, such IDE/SATA, format, size, make & model, etc...? thanks

4 3

How to Auto Add forward slash "/" when accessing a link/url through ProxyPass
by ankush grover 09 Jul '08

09 Jul '08

Hi Friends, I am using Centos 5.2 and using ProxyPass to access applications running on other servers. Everything is working fine except for one of the applications I need to auto add forward slash when any user tries to access that application. For ex ProxyPass /testdiary http://testdiary.example.com/ ProxyPassReverse /testdiary http://testdiary.example.com/ If somebody access directly http://testdiary.example.com/ everything is coming means the login page but when the same link is accessed through apache server on which proxypass is running then the login page does not appear(http://portal.example.com/testdiary). How can I auto add "/" when somebody put the url http://portal.example.com/testdiary which should first be converted/redirected to http://portal.example.com/testdiary/ (auto added forward slash). I have the below lines added in httpd.conf file RewriteEngine On RewriteCond %{REQUEST_URI} /testdiary RewriteRule /testdiary(.)$ /testdiary/ ProxyPass /testdiary http://testdiary.example.com/ ProxyPassReverse /testdiary http://testdiary.example.com/ Please let me know if you need any other information. Regards Ankush

3 3

sudoers
by Mário Gamito 09 Jul '08

09 Jul '08

Hi, I need to run /bin/mount and /sbin/mount.cifs commands as nobody user (it has (bin/bash shell). So, I've edited /etc/sudoers and added: Cmnd_Alias CMD_MOUNT = /bin/mount Cmnd_Alias CMD_CIFS ) = /sbin/mount.cifs nobody ALL = NOPASSWD: CMD_MOUNT nobody ALL = NOPASSWD: CMD_CIFS But when I run the command as nobody (in the shell), I get the error: "mount error 1 = Operation not permitted" Any ideas ? Any help would be appreciated. Warm Regards, Mário Gamito

3 5

how do I find out which nameserver returns a DNS query?
by Rudi Ahlers 09 Jul '08

09 Jul '08

Hi all If I do a "dig mydomain.co.za" from a Linux server, how do I know which DNS nameserver returns the queries? I seem to have a faulty DNS server, but can't see which one, so I want to find out which nameserver (if there's 4 - ns1.myserver, ns2.myserver, ns3.myserver & ns4.myserver) returns the queries? -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff

7 12

Centos4 audio problem
by lingu 09 Jul '08

09 Jul '08

Hi, I am running centos4u5 on dell precision m4300 laptop. I installed vlc player and i am able to watch the videos,but i am not able to hear audio.when i do system-config-soundcard i am getting the below error. system-config-soundcard Wrong card index 0... ALSA lib pcm_hw.c:1207:(_snd_pcm_hw_open) Invalid value for card aplay: main:550: audio open error: No such device My installed kernel and alsa rpm are uname -a Linux demo.xxx.com 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux rpm -qa |grep alsa alsa-driver-1.0.15-63.el4 alsa-lib-1.0.15-33.el4 alsa-lib-devel-1.0.15-33.el4 alsa-utils-1.0.13-22.el4.at Kindly tell me how to troubleshoot and make audio up and running on my centos box.

1 0

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

09 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. CESA-2008:0533 Important CentOS 5 x86_64 bind Update (Karanbir Singh) 2. CESA-2008:0533 Important CentOS 5 i386 bind Update (Karanbir Singh) 3. CESA-2008:0533 Important CentOS 5 i386 selinux-policy Update (Karanbir Singh) 4. CESA-2008:0533 Important CentOS 5 x86_64 selinux-policy Update (Karanbir Singh) 5. CESA-2008:0533 Important CentOS 4 i386 bind - security update (Karanbir Singh) 6. CESA-2008:0533 Important CentOS 4 x86_64 bind - security update (Karanbir Singh) 7. CESA-2008:0533-03: Important CentOS 2 i386 bind security update (John Newbigin) 8. CESA-2008:0533 Important CentOS 3 i386 bind - security update (Tru Huynh) 9. CESA-2008:0533 Important CentOS 3 x86_64 bind - security update (Tru Huynh) 10. CESA-2008:0584 Important CentOS 3 i386 pidgin - security and bug fix update (Tru Huynh) 11. CESA-2008:0584 Important CentOS 3 x86_64 pidgin - security and bug fix update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Tue, 8 Jul 2008 23:25:28 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 5 x86_64 bind Update To: centos-announce(a)centos.org Message-ID: <20080708222528.GA11254(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0533 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: c2c6d8ced889948d7a52fbbb577ec2ff bind-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 0c66970cb9b1b46e7f8210c638134ba7 bind-chroot-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 1a7ac4ce354fcec092883a9576b36df6 bind-devel-9.3.4-6.0.1.P1.el5_2.i386.rpm 8c583619590d9ed1eadb4eb051596b2e bind-devel-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 3619ebd7db64aca5233f8f8ee5257ad3 bind-libbind-devel-9.3.4-6.0.1.P1.el5_2.i386.rpm add59a4ea355f3a5d1419d1346f6291f bind-libbind-devel-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 82a6d9384889251bbb8be4ff8d219138 bind-libs-9.3.4-6.0.1.P1.el5_2.i386.rpm 933db16de4cf5a9e10020ae98a70c6b5 bind-libs-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 035d22d1efabef8132bd81b32d74c6e5 bind-sdb-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 131912b8adfd31fa4dee708c31cb8fe9 bind-utils-9.3.4-6.0.1.P1.el5_2.x86_64.rpm 88272fc94fa0931c921a07114eb43b76 caching-nameserver-9.3.4-6.0.1.P1.el5_2.x86_64.rpm Source: 04f1d50ade98e62d8e6ba7e1e10a628b bind-9.3.4-6.0.1.P1.el5_2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Tue, 8 Jul 2008 23:25:27 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 5 i386 bind Update To: centos-announce(a)centos.org Message-ID: <20080708222527.GA11240(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0533 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: c56c92553eb90170033acee5bb59452b bind-9.3.4-6.0.1.P1.el5_2.i386.rpm b29a740114dad7c05298c3d918d58d9f bind-chroot-9.3.4-6.0.1.P1.el5_2.i386.rpm 855467cb58da54de80247822582f9345 bind-devel-9.3.4-6.0.1.P1.el5_2.i386.rpm d6535a359503b0496e6fada794459f28 bind-libbind-devel-9.3.4-6.0.1.P1.el5_2.i386.rpm a4221403333d4dad042879ccabe06729 bind-libs-9.3.4-6.0.1.P1.el5_2.i386.rpm 716fc3382bb8f99e9edeb98d05d469db bind-sdb-9.3.4-6.0.1.P1.el5_2.i386.rpm e929b543e5f134aaa43cbe41afa95bce bind-utils-9.3.4-6.0.1.P1.el5_2.i386.rpm fbe6b53a396d842242834d5774756c15 caching-nameserver-9.3.4-6.0.1.P1.el5_2.i386.rpm Source: 04f1d50ade98e62d8e6ba7e1e10a628b bind-9.3.4-6.0.1.P1.el5_2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Tue, 8 Jul 2008 23:25:36 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 5 i386 selinux-policy Update To: centos-announce(a)centos.org Message-ID: <20080708222536.GA11275(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0533 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: ca1344838bf27d12d7c1a4828e648bb0 selinux-policy-2.4.6-137.1.el5.noarch.rpm 9d961613d0b4328a11c04ca74b551d22 selinux-policy-devel-2.4.6-137.1.el5.noarch.rpm d009023fb292837fe0fb0980814240b8 selinux-policy-mls-2.4.6-137.1.el5.noarch.rpm f942d8bb0c93cd548e92a7b9b8abb5d1 selinux-policy-strict-2.4.6-137.1.el5.noarch.rpm 0a0be1f04001cb21eeb654d2cf0f6aa5 selinux-policy-targeted-2.4.6-137.1.el5.noarch.rpm Source: e13395922af59c3d7d552e544d4640e4 selinux-policy-2.4.6-137.1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Tue, 8 Jul 2008 23:25:36 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 5 x86_64 selinux-policy Update To: centos-announce(a)centos.org Message-ID: <20080708222536.GA11288(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0533 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: dabb543cd24968481bcdf89e196d88be selinux-policy-2.4.6-137.1.el5.noarch.rpm 9694838cdbe7aefda0f0de1b0ad82322 selinux-policy-devel-2.4.6-137.1.el5.noarch.rpm 83e0a42fe02b9d4591506d8991b8b67a selinux-policy-mls-2.4.6-137.1.el5.noarch.rpm 855033e2d98af20f2149bc697d7bcb67 selinux-policy-strict-2.4.6-137.1.el5.noarch.rpm 226da98c5a3033d7647d2f781ce90a2a selinux-policy-targeted-2.4.6-137.1.el5.noarch.rpm Source: e13395922af59c3d7d552e544d4640e4 selinux-policy-2.4.6-137.1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Wed, 09 Jul 2008 00:19:01 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 4 i386 bind - security update To: centos-announce(a)centos.org Message-ID: <4873F5E5.8010009(a)centos.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: i386: bind-9.2.4-28.0.1.el4.i386.rpm bind-chroot-9.2.4-28.0.1.el4.i386.rpm bind-devel-9.2.4-28.0.1.el4.i386.rpm bind-libs-9.2.4-28.0.1.el4.i386.rpm bind-utils-9.2.4-28.0.1.el4.i386.rpm selinux-policy-targeted-1.17.30-2.150.el4.noarch.rpm selinux-policy-targeted-sources-1.17.30-2.150.el4.noarch.rpm src: bind-9.2.4-28.0.1.el4.src.rpm selinux-policy-targeted-1.17.30-2.150.el4.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 6 Date: Wed, 09 Jul 2008 00:20:21 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 4 x86_64 bind - security update To: centos-announce(a)centos.org Message-ID: <4873F635.8070804(a)centos.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: x86_64: bind-9.2.4-28.0.1.el4.x86_64.rpm bind-chroot-9.2.4-28.0.1.el4.x86_64.rpm bind-devel-9.2.4-28.0.1.el4.x86_64.rpm bind-libs-9.2.4-28.0.1.el4.i386.rpm bind-libs-9.2.4-28.0.1.el4.x86_64.rpm bind-utils-9.2.4-28.0.1.el4.x86_64.rpm selinux-policy-targeted-1.17.30-2.150.el4.noarch.rpm selinux-policy-targeted-sources-1.17.30-2.150.el4.noarch.rpm src: bind-9.2.4-28.0.1.el4.src.rpm selinux-policy-targeted-1.17.30-2.150.el4.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 7 Date: Wed, 09 Jul 2008 11:20:56 +1000 From: John Newbigin <jnewbigin(a)ict.swin.edu.au> Subject: [CentOS-announce] CESA-2008:0533-03: Important CentOS 2 i386 bind security update To: centos-announce(a)centos.org Message-ID: <48741278.4030106(a)ict.swin.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed The following errata for CentOS-2 have been built and uploaded to the centos mirror: RHSA-2008:0533-03 Important: bind security update Files available: bind-9.2.1-10.el2.i386.rpm bind-devel-9.2.1-10.el2.i386.rpm bind-utils-9.2.1-10.el2.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the latest patches is to run: # yum update -- John Newbigin ITS Senior Analyst / Programmer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin ------------------------------ Message: 8 Date: Wed, 9 Jul 2008 12:19:13 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0533 Important CentOS 3 i386 bind - security update To: centos-announce(a)centos.org Message-ID: <20080709101913.GB13258(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0533 bind security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/bind-9.2.4-22.el3.i386.rpm updates/i386/RPMS/bind-chroot-9.2.4-22.el3.i386.rpm updates/i386/RPMS/bind-devel-9.2.4-22.el3.i386.rpm updates/i386/RPMS/bind-libs-9.2.4-22.el3.i386.rpm updates/i386/RPMS/bind-utils-9.2.4-22.el3.i386.rpm source: updates/SRPMS/bind-9.2.4-22.el3.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update bind Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Re: [CentOS] NOW: Firefox 3.0 and GNOME crash when trying to view SME Server documentation WAS: OT: anything in CentOS 5.2 that uses opendns.com when browsing web?
by Lanny Marcus 09 Jul '08

09 Jul '08

On 7/8/08, Marko A. Jennings <markobiz(a)bluegargoyle.com> wrote: > On Tue, July 8, 2008 10:03 pm, Stephen John Smoogen wrote: >> On Tue, Jul 8, 2008 at 7:56 PM, Lanny Marcus <lmmailinglists(a)gmail.com> >> wrote: >>> On 7/8/08, Lanny Marcus <lmmailinglists(a)gmail.com> wrote: >>>> On Tue, Jul 8, 2008 at 8:00 PM, Ross Cavanagh >>>> <ross-cavanagh(a)bm-sms.co.jp> wrote: >>> <snip> >>>>>> >>>>> As for the SME documentation, you can select to view as one page >>>>> [the option is at the bottom of the page when you are browse to the >>>>> specific documentattion]. >>>>> >>>>> eg. >>>>> http://wiki.contribs.org/SME_Server:Documentation:Administration_Ma >>>>> nual:Booklet >>>>> >>>>> Then, you can print it to PDF if you want. >>>> >>>> >>>> Ross: I tried that, once before and it didn't work. I just tried it, >>>> again, after reading your post. Not only did Firefox 3.0 (which I got >>>> in an update today) crash, but I crashed out of GNOME, back to the >>>> login screen where you select which Desktop to use. I will send this >>>> reply and try it again. If I can get the SME Server documentation in >>>> one .pdf document on my hard drive, I'm quite interested in SME >>>> Server. Thanks. Lanny >>> >>> This is unrelated to the opendns.com thread that I began. There is >>> something wrong with GNOME and Firefox. At this time, I am using KDE >>> and Konqueror. I can view the SME Server document Ross has the link >>> for, without any problem, and without my browser and desktop crashing. >>> I haven't found the place where you view the entire document as one >>> page yet, but this is huge improvement, after having Firefox 3.0 and >>> GNOME crash, while trying to view the document. >> >> I can't replicate a crash. EG the infamous, it works for me. I think >> there is something up with your system/network. > > I can replicate it every time I try with Firefox under CentOS 5, but it > works fine with Konqueror. An EeePC and a laptop running Ubuntu don't > have any problems accessing this page with Firefox. > This is from /var/log/messages Jul 8 21:16:07 dell2400 dhclient: bound to 192.168.10.54 -- renewal in 1793 seconds. Jul 8 21:17:05 dell2400 restorecond: Will not restore a file with more than one hard link (/etc/resolv.conf) No such file or directory Jul 8 21:17:06 dell2400 gconfd (lanny-3906): Received signal 15, shutting down cleanly Jul 8 21:17:06 dell2400 gconfd (lanny-3906): Exiting Jul 8 21:17:24 dell2400 gconfd (lanny-4631): starting (version 2.14.0), pid 4631 user 'lanny' Jul 8 21:17:24 dell2400 gconfd (lanny-4631): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jul 8 21:17:24 dell2400 gconfd (lanny-4631): Resolved address "xml:readwrite:/home/lanny/.gconf" to a writable configuration source at position 1 Jul 8 21:17:24 dell2400 gconfd (lanny-4631): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jul 8 21:17:28 dell2400 gconfd (lanny-4631): Resolved address "xml:readwrite:/home/lanny/.gconf" to a writable configuration source at position 0 Jul 8 21:23:21 dell2400 gconfd (lanny-4631): Received signal 15, shutting down cleanly Jul 8 21:23:21 dell2400 gconfd (lanny-4631): Exiting Jul 8 21:23:21 dell2400 gconfd (lanny-5055): starting (version 2.14.0), pid 5055 user 'lanny'

4 3

Problems with some rpms in my local repo
by Robert Moskowitz 09 Jul '08

09 Jul '08

This is perplexing. on a Centos 5.1 box that I am trying to upgrade, I keep getting: [Errno 4] IOError: <urlopen error unknown url type: media> from my local repo. I did a blank system install via http from this server with no problem. For instance, if I limit myself to: yum upgrade yum I get: Loading "priorities" plugin Loading "installonlyn" plugin Setting up Upgrade Process Setting up repositories Reading repository metadata in from local files 0 packages excluded due to repository priority protections Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package yum.noarch 0:3.2.8-9.el5.centos.2.1 set to be updated --> Running transaction check --> Processing Dependency: yum-metadata-parser >= 1.1.0 for package: yum --> Processing Dependency: yum-fastestmirror for package: yum --> Processing Dependency: python-iniparse for package: yum --> Processing Dependency: yum = 3.0.5-1.el5.centos.5 for package: yum-updatesd --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Downloading header for yum-metadata-parser to pack into transaction set. media://1213888991.267240%231/CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm: [Errno 4] IOError: <urlopen error unknown url type: media> Trying other mirror. Error: failed to retrieve CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm from base error was [Errno 4] IOError: <urlopen error unknown url type: media> Yet on the system I built, yum-metadata-parser-1.1.2-2.el5.i386.rpm is there, and I have done a yum update on that system already (how I learned there are bunches of updates out there). I suggestions on how to troubleshoot this? BTW, I did a yum upgrade kernel* and that worked fine. I was going to try to upgrade piece-by-piece, as this is a slow box.

10 19

← Newer
1
...
30
31
32
33
34
35
36
...
44
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2008