Discuss

discuss@lists.centos.org

34758 discussions

Good evening to all
by Silambarasan.R 30 Nov '07

30 Nov '07

Hi.. Could u help me to re-install the centos 4 without affecting existing data...? is it possible? if so pl let me know... Regards Silambu.R

3 2

Re: [CentOS] CleanLog.h
by B.J. McClure 30 Nov '07

30 Nov '07

On Fri, 2007-11-30 at 07:40 -0500, Alfredo Perez wrote: > On Thu, Nov 29, 2007 at 04:43:44PM -0600, B.J. McClure wrote: > > Sad to say one of my file servers was exploited and used to run a > > Phishing scam. Have identified subject virus amongst other things. It > > appears twice in a virus scan; /sbin/z (which I assume can just be > > deleted) and /sys/bus/serio/drivers/atkbd/description. The latter file > > is also present in identical uninfected machines. I have been unable to > > open the file, even with root privileges, although it appears to be a > > text file. Any suggestions on how to proceed appreciated. Guess I > > could delete it and copy over the file from an identical machine. > > > > Thanks in advance, > > B.J. > > > > CentOS 5.0, Linux 2.6.18-8.1.15.el5 x86_64 16:26:48 up 10:46, 1 user, > > load average: 0.07, 0.08, 0.04 > > Hi Can you tell me which virus scan you are using? > > Thanks avg75flr-r49-a1130.i386.rpm B.J. CentOS 5.0, Linux 2.6.18-8.1.15.el5 x86_64 07:26:34 up 1 day, 1:45, 1 user, load average: 0.30, 0.13, 0.09

1 0

CleanLog.h
by B.J. McClure 30 Nov '07

30 Nov '07

Sad to say one of my file servers was exploited and used to run a Phishing scam. Have identified subject virus amongst other things. It appears twice in a virus scan; /sbin/z (which I assume can just be deleted) and /sys/bus/serio/drivers/atkbd/description. The latter file is also present in identical uninfected machines. I have been unable to open the file, even with root privileges, although it appears to be a text file. Any suggestions on how to proceed appreciated. Guess I could delete it and copy over the file from an identical machine. Thanks in advance, B.J. CentOS 5.0, Linux 2.6.18-8.1.15.el5 x86_64 16:26:48 up 10:46, 1 user, load average: 0.07, 0.08, 0.04

4 3

CentOS-announce Digest, Vol 33, Issue 15
by centos-announce-request＠centos.org 30 Nov '07

30 Nov '07

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-2007:1084 Critical CentOS 3 i386 seamonkey - security update (Tru Huynh) 2. CESA-2007:1084 Critical CentOS 3 x86_64 seamonkey - security update (Tru Huynh) 3. CESA-2007:1082 Critical CentOS 3 i386 firefox - security update (CENTOSPLUS only) (Tru Huynh) 4. CESA-2007:1082 Critical CentOS 3 x86_64 firefox - security update (CENTOSPLUS only) (Tru Huynh) 5. CESA-2007:1084 Critical CentOS 3 s390(x) seamonkey - security update (Pasi Pirhonen) 6. CESA-2007:1063 Important CentOS 3 ia64 pcre - security update (Pasi Pirhonen) 7. CESA-2007:1063 Important CentOS 3 s390(x) pcre - security update (Pasi Pirhonen) 8. CESA-2007:1068 Important CentOS 4 ia64 pcre - security update (Pasi Pirhonen) 9. CESA-2007:1063 Important CentOS 3 i386 pcre - security update (Tru Huynh) 10. CESA-2007:1063 Important CentOS 3 x86_64 pcre - security update (Tru Huynh) 11. CESA-2007:1068 Important CentOS 4 s390(x) pcre - security update (Pasi Pirhonen) 12. CESA-2007:1084-01: Critical CentOS 2 i386 seamonkey security update (John Newbigin) 13. CESA-2007:1065-01: Moderate CentOS 2 i386 pcre security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Thu, 29 Nov 2007 14:04:23 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2007:1084 Critical CentOS 3 i386 seamonkey - security update To: centos-announce(a)centos.org Message-ID: <20071129130423.GA19200(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2007:1084 seamonkey security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2007-1084.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/seamonkey-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-chat-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-devel-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-dom-inspector-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-js-debugger-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-mail-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-nspr-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-nspr-devel-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-nss-1.0.9-0.7.el3.centos3.i386.rpm updates/i386/RPMS/seamonkey-nss-devel-1.0.9-0.7.el3.centos3.i386.rpm source: updates/SRPMS/seamonkey-1.0.9-0.7.el3.centos3.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update seamonkey Tru -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Persist perms on devices after reboots
by Tom Brown 30 Nov '07

30 Nov '07

Hi Dumb question i think but how can i make devices permissions persist after a reboot. I dont think i have come across this issue before but i have some SAN disks that need to be oracle:dba as their perms but after a reboot they reset back to brw------- 1 root root 120, 49 Nov 30 10:40 /dev/emcpowerd1 any thoughts? thanks

2 1

kernel-2.6.9-55.0.12.EL not booting (lvm? 3ware?)
by Ugo Bellavance 30 Nov '07

30 Nov '07

Hi, Here's he setup. Original Kernel: kernel-smp-2.6.9-42.EL, booting fine. Error with kernel-2.6.9-55.0.12.EL (and kernel-2.6.9-55.0.12.ELsmp) No volume groups found Volume group "VolGroup00" not found. ERROR: /bin/lvm exited abnormally! The system has a 3ware 9000 Storage Controller Model: 9500S-4LP Firmware FE9X 2.08.00.006, BIOS BE9X 2.03.01.052, Ports: 4. Anyone seen this? I've googled but can't find anything, except that: [184523] -add support for 3ware 9650SE SATA-RAID (Chip Coldwell) ... in 2.6.9-44 Regards, Ugo

3 2

Stuck at GRUB
by Ugo Bellavance 30 Nov '07

30 Nov '07

Hi, I have a Dell poweredge 400SC here with an LSI scsi card. I installed Centos4 a while ago and put it in a datacenter. I rebooted many weeks after, and the machine didn't come back up. So I went to the datacenter tonight to find out that the server was stuck at "GRUB". Nothing more. So I decided to re-install Centos4. The partitions were already there, so I just made sure partitions were formatted and the install went fine. When I rebooted, "GRUB". I'm at this point and I don't know exactly what I could do to diagnose furthere. Any ideas? Regards, Ugo

7 19

ieee1394 firewire disk unable to see or mount [SEC=UNCLASSIFIED]
by Lawson Hanson 30 Nov '07

30 Nov '07

We have some LaCie 1 TB external disks which work fine on other Linux servers (running Red Hat 9, and Ubuntu 7.04), but which fail to be seen on our CentOS 4.3 system with kernel 2.6.9-34.107.plus.c4smp The interface card is a Sunix 64 bit Firewire 800 ieee1394b adapter plugged into a PCI slot in our Linux server, which is a Tyan Thunder K8SD Pro S2882-D, 64 bit AMD Opteron CPU Using "cat" to examine the "/proc/scsi/scsi" information shows our system hard disk and internal RAID array: cat /proc/scsi/scsi ------------------- Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: WDC WD360GD-00FL Rev: 33.0 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi4 Channel: 00 Id: 00 Lun: 00 Vendor: AMCC Model: 9550SX-8LP DISK Rev: 3.01 Type: Direct-Access ANSI SCSI revision: 03 I have found various items in the centos list archives, but none of these has provided a definitive solution; I have used commands such as "lspci", and "lsmod" to ensure that the system sees the firewire card, and has iee1394 and other modules loaded: lspci | grep 1394 ----------------- 01:03.0 Firewire (IEEE 1394): Texas Instruments TSB82AA2 \ IEEE-1394b Link Layer Controller (rev 01) lsmod | egrep '1394|sbp2|s.*_mod' --------------------------------- sbp2 26825 0 ohci1394 36953 0 ieee1394 124601 2 sbp2,ohci1394 sd_mod 19393 7 scsi_mod 140561 4 sbp2,3w_9xxx,libata,sd_mod Somewhere I found a note about trying the "serialize_io=1" option with the "sbp2" module, and now have tried that, but still have no joy: dmesg | grep sbp ---------------- sbp2: $Rev: 1219 $ Ben Collins <bcollins(a)debian.org> sbp2: $Rev: 1219 $ Ben Collins <bcollins(a)debian.org> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) The "1394" messages in "dmesg" are: dmesg | grep 1394 ----------------- ieee1394: Initialized config rom entry `ip1394' ohci1394: $Rev: 1223 $ Ben Collins <bcollins(a)debian.org> ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[209] \ MMIO=[fc7fe800-fc7fefff] Max Packet=[4096] ieee1394: Host added: ID:BUS[0-00:1023] GUID[080028560000470a] ieee1394: Error parsing configrom for node 0-01:1023 ieee1394: The root node is not cycle master capable; \ selecting a new root node and resetting... ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-00:1023 -> 0-01:1023 ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-01:1023 -> 0-00:1023 ieee1394: Error parsing configrom for node 0-01:1023 ieee1394: The root node is not cycle master capable; \ selecting a new root node and resetting... ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Error parsing configrom for node 0-01:1023 ieee1394: The root node is not cycle master capable; \ selecting a new root node and resetting... ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Node changed: 0-00:1023 -> 0-01:1023 ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) If anyone can suggest how I might proceed to get our LaCie disks to run on the Firewire card under CentOS 4.3, I shall be delighted to see what I need to do, thanks Best regards, Lawson Hanson ------ Climate Change Group Centre for Australian Weather and Climate Research

1 0

Re: [CentOS] CleanLog.h
by Ross S. W. Walker 30 Nov '07

30 Nov '07

Find out how they got in and make sure that hole is fixed. Do an rpm verify on all installed packages (excluding configs), reinstall the rpms that fail the verify. Find all binaries that are not accountable in rpm and nuke them. Harden your host with selinux and audit, keep audit logs of all changes to binary files and essential configs and make sure the audit logs are immutable. Keep an eye on the system for a while to make sure you haven't missed anything. Keep LVM snapshots of your OS LVs. -Ross -----Original Message----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Thu Nov 29 17:43:44 2007 Subject: [CentOS] CleanLog.h Sad to say one of my file servers was exploited and used to run a Phishing scam. Have identified subject virus amongst other things. It appears twice in a virus scan; /sbin/z (which I assume can just be deleted) and /sys/bus/serio/drivers/atkbd/description. The latter file is also present in identical uninfected machines. I have been unable to open the file, even with root privileges, although it appears to be a text file. Any suggestions on how to proceed appreciated. Guess I could delete it and copy over the file from an identical machine. Thanks in advance, B.J. CentOS 5.0, Linux 2.6.18-8.1.15.el5 x86_64 16:26:48 up 10:46, 1 user, load average: 0.07, 0.08, 0.04 ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

3 2

Re: [CentOS] special tricks for developers box on centos 5
by Ross S. W. Walker 29 Nov '07

29 Nov '07

More importantly, mount your dev filesys with atimes disabled and ext3 indexing on. Use tmpfs for /tmp, /usr/tmp, /var/tmp, it uses swappable ram filesys which helps a lot too. Make sure nothing gets put in those tmp dirs that needs to persist across a reboot and limit the max size each can take to 1/2 total memory. More memory... As far as background jobs go, reschedule them for day time hours when your asleep ;-) -Ross -----Original Message----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Thu Nov 29 18:26:56 2007 Subject: Re: [CentOS] special tricks for developers box on centos 5 Jerry, --- Jerry Geis <geisj(a)pagestation.com> wrote: > I was just wondering if there are special tricks > people do > that compile A LOT on centos? Do RAM disks help or > something else I dont > about that minimizes your compile time? I presently > have and AMD x2 > 4800+ with 2GIG ram. > > Just curious if I can reduce any more time out of my > compiles. Watch out for background processes that steal resources: Move /etc/cron.daily/ mlocate prelink to /etc/cron.weekly Remove /etc/cron.daily/makewhatis and let it only run weekly (its already in weekly) Open /etc/updatedb and tune it for your system: add ntfs-3g or vfat to prunefs If you have any mock partitions, add that to prunepath -- Mark My C5 repo with RequestTracker http://www.tlviewer.org/centos ____________________________________________________________________________________ Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

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