Discuss

discuss@lists.centos.org

34758 discussions

CentOS-announce Digest, Vol 43, Issue 1
by centos-announce-request＠centos.org 01 Sep '08

01 Sep '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:0875-03: Low CentOS 2 i386 tzdata enhancement update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Mon, 01 Sep 2008 09:51:22 +1000 From: John Newbigin <jnewbigin(a)ict.swin.edu.au> Subject: [CentOS-announce] CESA-2008:0875-03: Low CentOS 2 i386 tzdata enhancement update To: centos-announce(a)centos.org Message-ID: <48BB2E7A.2080609(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: RHEA-2008:0875-03 tzdata enhancement update Files available: tzdata-2008e-1.el2_1.noarch.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 ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 43, Issue 1 **********************************************

1 0

S.M.A.R.T
by Mag Gam 01 Sep '08

01 Sep '08

At my physics lab we have 30 servers with 1TB disk packs. I am in need of monitoring for disk failures. I have been reading about SMART and it seems it can help. However, I am not sure what to look for if a drive is about to fail. Any thoughts about this? Is anyone using this method to predetermine disk failures? TIA

5 13

Iptables masq traffic limiting
by Joseph L. Casale 01 Sep '08

01 Sep '08

Where is the correct place to control what traffic is masq'ed out? This is what I have, but I was told the Forward chain isn't the right place to do this? iptables -A POSTROUTING -t nat -o $WAN -j MASQUERADE iptables -A FORWARD -i $WAN -o $LAN -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A FORWARD -i $LAN -o $WAN -m state --state NEW,ESTABLISHED,RELATED -p tcp -m multiport --dports 80,443 -j ACCEPT So which table is the theoretically correct place to add all the ports/services I would want masq'ed out for internal clients? Thanks! jlc

3 8

strange httpd error page using apache
by Ric Moore 01 Sep '08

01 Sep '08

I get this error page re-direct while opening a local webpage on my server, which carries me to yahoo for the error page filled with adverts. I'd really like to know how this one got here, as I just installed centOS a few weeks ago. http://wwwwh.found-not-help.com/search?qo=www.wayward4now.net&rn=3D9F6PY8wd… This just doesn't strike me as Kosher. And, I'm a southern baptist! <grins> Ric

2 3

rc.local
by Ric Moore 01 Sep '08

01 Sep '08

I note that there are two 'rc.local' files. One is in /etc and the other in /etc/rc.d Which has precedence and is the one to use? Thanks, Ric

3 3

LVM and hotswap (USB/iSCSI) devices?
by Simen Timian Thoresen 31 Aug '08

31 Aug '08

Hi list, I'm having one of those 'I'm stupid' -problems with LVM on CentOS 5.2. I've been working with traditional partitions until now, but I've finally been sold on the theoretical benefits of using LVM, but for now I only have a huge pile of broken filesystems to show for my efforts. My scenario; I attach a disk, either over USB or iSCSI. I create a PV on this device, create a VG using the device, and slice off a tiny LV for tests. [root@kasse ~]# dmesg usb 1-3: new high speed USB device using ehci_hcd and address 7 usb 1-3: configuration #1 chosen from 1 choice scsi27 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 7 usb-storage: waiting for device to settle before scanning Vendor: ST375064 Model: 0A Rev: 3.AA Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdg: 1465149168 512-byte hdwr sectors (750156 MB) sdg: Write Protect is off sdg: Mode Sense: 10 00 00 00 sdg: assuming drive cache: write through SCSI device sdg: 1465149168 512-byte hdwr sectors (750156 MB) sdg: Write Protect is off sdg: Mode Sense: 10 00 00 00 sdg: assuming drive cache: write through sdg: sdg1 sd 27:0:0:0: Attached scsi disk sdg sd 27:0:0:0: Attached scsi generic sg6 type 0 usb-storage: device scan complete [root@kasse ~]# pvcreate /dev/sdg1 Physical volume "/dev/sdg1" successfully created [root@kasse ~]# vgcreate testgroup /dev/sdg1 Volume group "testgroup" successfully created [root@kasse ~]# lvcreate -L 200M testgroup -n testLV Logical volume "testLV" created At this point, I have /dev/testgroup/testLV, which I can stick a fs on, mount, store files on, unmount, remount and recover the files from. Just as I'd expect. [root@kasse ~]# lvdisplay --- Logical volume --- LV Name /dev/testgroup/testLV VG Name testgroup LV UUID 3KjDiZ-gTAD-sC9E-sOSA-772o-41Yk-ZKK7cx LV Write Access read/write LV Status available # open 0 LV Size 200.00 MB Current LE 50 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 I have not explicitly set the vg active, as I understand that it implicitly will be set active in non-clustered environments like mine. LVM works as I'd expect it to up until here in any case. So - with the LV unmounted, I power my USB-device down, and then back up; [root@kasse ~]# dmesg usb 1-3: USB disconnect, address 7 usb 1-3: new high speed USB device using ehci_hcd and address 8 usb 1-3: configuration #1 chosen from 1 choice scsi28 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 8 usb-storage: waiting for device to settle before scanning Vendor: ST375064 Model: 0A Rev: 3.AA Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdi: 1465149168 512-byte hdwr sectors (750156 MB) sdi: Write Protect is off sdi: Mode Sense: 10 00 00 00 sdi: assuming drive cache: write through SCSI device sdi: 1465149168 512-byte hdwr sectors (750156 MB) sdi: Write Protect is off sdi: Mode Sense: 10 00 00 00 sdi: assuming drive cache: write through sdi: sdi1 sd 28:0:0:0: Attached scsi disk sdi sd 28:0:0:0: Attached scsi generic sg6 type 0 usb-storage: device scan complete (note that my disk is now sdi, not sdg, and connected on scsi28 and not scsi27) If I now try to access the device, all falls appart; [root@kasse ~]# lvdisplay /dev/testgroup/testLV: read failed after 0 of 4096 at 209649664: Input/output error /dev/testgroup/testLV: read failed after 0 of 4096 at 209707008: Input/output error /dev/testgroup/testLV: read failed after 0 of 4096 at 0: Input/output error /dev/testgroup/testLV: read failed after 0 of 4096 at 4096: Input/output error /dev/testgroup/testLV: read failed after 0 of 4096 at 0: Input/output error --- Logical volume --- LV Name /dev/testgroup/testLV VG Name testgroup LV UUID 3KjDiZ-gTAD-sC9E-sOSA-772o-41Yk-ZKK7cx LV Write Access read/write LV Status available # open 0 LV Size 200.00 MB Current LE 50 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 Trying to mount or otherwise access the LV also shows the problems; scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device printk: 25 messages suppressed. Buffer I/O error on device dm-1, logical block 30 Buffer I/O error on device dm-1, logical block 31 scsi 27:0:0:0: rejecting I/O to dead device Buffer I/O error on device dm-1, logical block 0 Buffer I/O error on device dm-1, logical block 1 Buffer I/O error on device dm-1, logical block 2 Buffer I/O error on device dm-1, logical block 3 Buffer I/O error on device dm-1, logical block 4 Buffer I/O error on device dm-1, logical block 5 Buffer I/O error on device dm-1, logical block 6 Buffer I/O error on device dm-1, logical block 7 scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device scsi 27:0:0:0: rejecting I/O to dead device hfs: unable to find HFS+ superblock So - LVM seems to believe my LV is still attached to scsi27, while it now actually sits on scsi28. What am I missing here? How do I get LVM to use a persistent device instead of a transient path? Yours, -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support

3 4

Re: [CentOS] wireless laptop configuration
by Toshaan Bharvani 31 Aug '08

31 Aug '08

Sorin Srbu wrote: From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Toshaan Bharvani Sent: Tuesday, August 19, 2008 4:24 PM To: centos(a)centos.org Subject: Re: [CentOS] wireless laptop configuration Sorin Srbu wrote: From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Toshaan Bharvani Sent: Tuesday, August 19, 2008 2:42 PM To: centos(a)centos.org Subject: Re: [CentOS] wireless laptop configuration Steve Huff wrote: > > On Aug 19, 2008, at 5:04 AM, Sorin@Gmail wrote: > >> I'm using a 3Com 3CRWE154G72 IIRC, which according to the hwconf's using the >> prism54 driver/firmware/whatever. >> >> Would I maybe be better off reinstalling the whole shebang and have the >> wifi-card inserted from start in order for the centos installer to >> see it >> properly from the beginning? > > > before you do that, open a terminal, become root, and run > /usr/sbin/kudzu (while the wireless card is installed). that's the > program that does hardware detection; it may be able to sort out your > issue. > > -steve > or if kudzu for some reason doesn't cooperate (which is always on my system) become root run : /sbin/modprobe prism54 run : dmesg | tail and read whether it just says it has loaded the module (single line) or detected will output a wlanX statement and you are in business Isn’t it implied that since ”prism54” is listed in /etc/sysconfig/hwconf for the wifi-card that the module has been loaded already? Or is this some of the magical stuff that sometimes doesn’t happen for whatever reason? 8-) /etc/sysconfig/hwconf is the file kudzu creates when of all detected hardware at startup and it related this hardware with drivers in the kernel but certain drivers are modules in the kernel, wich need to be loaded manually or later when the system is already running this can be done by method 1 explained here above or adding them in /etc/modprobe.conf which makes it load the modules at startup you will need to add the line (if it is not yet there) : alias wlan0 prism54 you can check whether the module is loaded with : /sbin/lsmod | grep prism54 This is how far I got with the above hints. For some reason I don’t have a wlan0, but instead a eth0. I did create an alias in Network Manager for eth0 > wlan0. Then I ran the below modprobe command according to the below. “[root@centos-v5-x86 ~]# /sbin/modprobe prism54 [root@centos-v5-x86 ~]# dmesg|tail eth0: resetting device... eth0: uploading firmware... prism54: request_firmware() failed for 'isl3890' eth0: could not upload firmware ('isl3890') eth0: islpci_reset: failure eth0: resetting device... eth0: uploading firmware... prism54: request_firmware() failed for 'isl3890' eth0: could not upload firmware ('isl3890') eth0: islpci_reset: failure [root@centos-v5-x86 ~]#” “When I try to activate wlan0, I get this message: Error for wireless request "Set Bit Rate" (8B20) : SET failed on device eth0 ; Input/output error. Determining IP information for eth0...SIOCSIFFLAGS: No such file or directory SIOCSIFFLAGS: No such file or directory failed.” In /etc/modprobe.conf I’ve added the line “alias wlan0 prism54”. What’s more, I went to the prism54.org site and found a firmware, downloaded it and as per instructed on the site, renamed the .arm-file to isl3890 and put it in /usr/lib/hotplug/firmware. Upon restarting and activating wlan0 I still get the above SIOC-error. I have a hunch this might actually work if I put the isl3890-file in the correct place. Not sure /usr/lib/hotplug/firmware *is* actually right, as I had to create the hotplugs and firmware-folders. Any hints on this guys? TIA. _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos you have used the following : 2.5.2.0.arm : http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.5.2.0.arm Version 2.5.2.0 built on Thu Mar 4 16:05:03 CET 2004 by inlbuild@tix 87a5519d70c16991b8fff9b3b31de68e headers Source: 3CRWE154G72_Jul_08_04.exe try renaming to isl3886 as it is a pcmcia card so it is equal to a pci version and then put in in /lib/firmware _________________________________________________________________ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx…

2 1

establish a 128 bit encrypted tunnel between centos 5.2 boxes
by Jerry Geis 31 Aug '08

31 Aug '08

Is there an easy way or anyway to establish a 128 bit encrypted tunnel between a handful of centos 5.2 boxes? I am not familiar with this at all. Jerry

10 11

CentOS-announce Digest, Vol 42, Issue 13
by centos-announce-request＠centos.org 31 Aug '08

31 Aug '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:0849 Important CentOS 3 ia64 ipsec-tools - security update (Pasi Pirhonen) 2. CESA-2008:0863 Important CentOS 3 ia64 libtiff - security update (Pasi Pirhonen) 3. CESA-2008:0849 Important CentOS 4 ia64 ipsec-tools - security update (Pasi Pirhonen) 4. CESA-2008:0848 Important CentOS 4 ia64 libtiff - security update (Pasi Pirhonen) 5. CESA-2008:0849 Important CentOS 3 s390(x) ipsec-tools - security update (Pasi Pirhonen) 6. CESA-2008:0863 Important CentOS 3 s390(x) libtiff - security update (Pasi Pirhonen) 7. CESA-2008:0849 Important CentOS 4 s390(x) ipsec-tools - security update (Pasi Pirhonen) 8. CESA-2008:0848 Important CentOS 4 s390(x) libtiff - security update (Pasi Pirhonen) 9. CESA-2008:0835 Important CentOS 5 i386 openoffice.org Update (Karanbir Singh) 10. CESA-2008:0835 Important CentOS 5 x86_64 openoffice.org Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Sat, 30 Aug 2008 17:16:28 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0849 Important CentOS 3 ia64 ipsec-tools - security update To: centos-announce(a)centos.org Message-ID: <20080830141628.GI9914(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2008:0849 https://rhn.redhat.com/errata/RHSA-2008-0849.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/ipsec-tools-0.2.5-0.7.rhel3.5.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

CentOS-announce Digest, Vol 42, Issue 12
by centos-announce-request＠centos.org 30 Aug '08

30 Aug '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:0863 Important CentOS 3 i386 libtiff - security update (Tru Huynh) 2. CESA-2008:0863 Important CentOS 3 x86_64 libtiff - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 29 Aug 2008 23:30:43 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0863 Important CentOS 3 i386 libtiff - security update To: centos-announce(a)centos.org Message-ID: <20080829213043.GA8571(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0863 libtiff security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0863.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/libtiff-3.5.7-31.el3.i386.rpm updates/i386/RPMS/libtiff-devel-3.5.7-31.el3.i386.rpm source: updates/SRPMS/libtiff-3.5.7-31.el3.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update libtiff Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

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