Discuss

discuss@lists.centos.org

34758 discussions

replacing a line in a file
by Jerry Geis 25 Jan '09

25 Jan '09

I have a large file that has a line like: bindaddr=0.0.0.0 ; some other text I want to replace the 0.0.0.0 with my address 192.168.1.8 and remove everything else on the line to get: bindaddr=192.168.1.8 How can I do that? Thanks, jerry

3 3

Problem detecting HP Tape Drive
by Mehdi Sarmadi 24 Jan '09

24 Jan '09

Hello I do have problem using Linux with an external HP tape drive. The server platform is also an HP Server; the server is an HP ML350 G4, and the Tape drive is a HP Storage Works Ultrium 448 - 1U Rack-mountable. HP Ultrium documentation says two drivers should be automatically up, sym53c8xx for LSI SCSI interface "st" for tape and /proc/scsi/scsi should contain information about tape drive, e.g. SCSI ID. However none of them happened in my case! (document: "UP LTO Ultrium 2-3 - Unix Config Guide") The SCSI adapter is an LSI53C1030. The system has another the same adapter which is used for hard disk drives. The interesting part is, the hard disk are detected and even OS boots from them, but I can't make the tape drive work. Moreover, in system boot up, LSI SCSI BIOS displays informations saying there is a tape drive connected! Any one has same experience, suggestion, comments or clues? I've place a zip file here: http://msarmadi.googlepages.com/report_files.zip which contains: - dmesg - lshal - lsmod - lspci -vv - cat /proc/scsi/scsi > proc.scsi.scsi - cat /proc/modules > proc.modules - uname -a > uname Also, below there are detailed information about devices and OS config/log files. ===== System info: Operating System: Redhat Enterprise Linux AS 5(the same thing happened using CentOS 5.2) Sever System: HP ML530 G4 SCSI Adapter: LSI 1030 Tape Drive: HP Storage Works Ultrium 448 - 1U Rack-mountable SCSI Cable: P/N 313375002 Rev R (coming with tape drive) *Note that, no other SCSI devices are connected to the cable. ===== Here is some parts of boot up messages on the screen of HP ML350 G4 ==== System BIOS D17 (14/04/2005) ... MPTBIOS-5.05.18 ... Slot 3 HP Smart Array 6400 Controller (192MB, v.2.26) 1 Logic Drive Detected 1794-Slot 3 Drive Arraye - Array Accelerator Battery Charge low Array Accelerator Posted-Write Cache is temporarilty Disabled Array Accelerator batteries hace failed to charge and should be replaced Slot 3 HP Smart Array 6400 EM Controller (192MB, v.2.26) 1 Logic Drive Detected Tape or CD-ROM Drive(s) Detected: SCSI Port 2: SCSI ID 1 1785-Slot 3 Drive Arraye Not Configured No Drives Detected ... [Followed by GRUB and Linux boot up] ========================= -- Mehdi Sarmadi

5 8

CentOS-announce Digest, Vol 47, Issue 9
by centos-announce-request＠centos.org 24 Jan '09

24 Jan '09

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-2009:0004 Important CentOS 4 i386 openssl security update (Karanbir Singh) 2. CESA-2009:0004 Important CentOS 4 x86_64 openssl security update (Karanbir Singh) 3. CESA-2009:0057 Important CentOS 5 i386 squirrelmail Update (Karanbir Singh) 4. CESA-2009:0057 Important CentOS 5 x86_64 squirrelmail Update (Karanbir Singh) 5. CESA-2009:0057 Important CentOS 4 i386 squirrelmail security update (Karanbir Singh) 6. CESA-2009:0057 Important CentOS 4 x86_64 squirrelmail security update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 Jan 2009 21:39:53 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:0004 Important CentOS 4 i386 openssl security update To: centos-announce(a)centos.org Message-ID: <20090123213953.GA10367(a)vkalu.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:0004 Important https://rhn.redhat.com/errata/RHSA-2009-0004.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: openssl-0.9.7a-43.17.el4_7.2.i386.rpm openssl-0.9.7a-43.17.el4_7.2.i686.rpm openssl-devel-0.9.7a-43.17.el4_7.2.i386.rpm openssl-perl-0.9.7a-43.17.el4_7.2.i386.rpm src: openssl-0.9.7a-43.17.el4_7.2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos @irc.freenode.net ------------------------------ Message: 2 Date: Fri, 23 Jan 2009 21:39:54 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:0004 Important CentOS 4 x86_64 openssl security update To: centos-announce(a)centos.org Message-ID: <20090123213954.GA10380(a)vkalu.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:0004 Important https://rhn.redhat.com/errata/RHSA-2009-0004.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: openssl-0.9.7a-43.17.el4_7.2.i686.rpm openssl-0.9.7a-43.17.el4_7.2.x86_64.rpm openssl-devel-0.9.7a-43.17.el4_7.2.i386.rpm openssl-devel-0.9.7a-43.17.el4_7.2.x86_64.rpm openssl-perl-0.9.7a-43.17.el4_7.2.x86_64.rpm src: openssl-0.9.7a-43.17.el4_7.2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos @irc.freenode.net ------------------------------ Message: 3 Date: Sat, 24 Jan 2009 06:16:17 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:0057 Important CentOS 5 i386 squirrelmail Update To: centos-announce(a)centos.org Message-ID: <20090124061617.GA12131(a)vkalu.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:0057 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2009-0057.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 2509185832b13f153462b6aad4eceb40 squirrelmail-1.4.8-5.el5.centos.3.noarch.rpm Source: 16b0a61a00c16c7a6b8f49123a0a7172 squirrelmail-1.4.8-5.el5.centos.3.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Sat, 24 Jan 2009 06:16:18 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:0057 Important CentOS 5 x86_64 squirrelmail Update To: centos-announce(a)centos.org Message-ID: <20090124061618.GA12147(a)vkalu.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:0057 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2009-0057.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 700a7599bab0d434eeb9ea714b029cf0 squirrelmail-1.4.8-5.el5.centos.3.noarch.rpm Source: 16b0a61a00c16c7a6b8f49123a0a7172 squirrelmail-1.4.8-5.el5.centos.3.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Sat, 24 Jan 2009 06:18:34 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:0057 Important CentOS 4 i386 squirrelmail security update To: centos-announce(a)centos.org Message-ID: <20090124061834.GA12197(a)vkalu.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:0057 Important https://rhn.redhat.com/errata/RHSA-2009-0057.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: squirrelmail-1.4.8-5.el4.centos.3.noarch.rpm src: squirrelmail-1.4.8-5.el4.centos.3.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos @irc.freenode.net ------------------------------ Message: 6 Date: Sat, 24 Jan 2009 06:18:35 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:0057 Important CentOS 4 x86_64 squirrelmail security update To: centos-announce(a)centos.org Message-ID: <20090124061835.GA12210(a)vkalu.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:0057 Important https://rhn.redhat.com/errata/RHSA-2009-0057.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: squirrelmail-1.4.8-5.el4.centos.3.noarch.rpm src: squirrelmail-1.4.8-5.el4.centos.3.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos @irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 47, Issue 9 **********************************************

1 0

file: /etc/sysconfig/clock
by chloe K 24 Jan '09

24 Jan '09

Hi I modify this file /etc/sysconfig/clock How can I restart the service to have update clock? Thank you --------------------------------- All new Yahoo! Mail - Get a sneak peak at messages with a handy reading pane.

2 1

Single Session VNC
by karl balsmeier 24 Jan '09

24 Jan '09

Currently most machines I connect to use a display, but I want to run vncserver such that the display is always 0. Is this possible.

2 1

svnserve with SASL on CentOS 5.2
by Ruslan Sivak 23 Jan '09

23 Jan '09

Hello List. I'm cross posting this from svn-users, as I'm not sure whether this is an CentOS specific issue. Perhaps someone here has an idea of what's going on? ----------------------------- I got a fresh install of CentOS 5.2 x32, svnserve, version 1.5.5 (r34862), here is my svnserve.conf file [general] anon-access = none auth-access = write realm = isf [sasl] use-sasl = true min-encryption = 128 max-encryption = 256 and here is my /etc/sasl2/svn.conf file pwcheck_method: auxprop auxprop_plugin: sasldb sasldb_path: /svn/sassl mech_list: DIGEST-MD5 On the client I am using TortoiseSVN 1.5.5 (TortoiseSVN 1.5.5, Build 14361 - 64 Bit , 2008/10/24 18:06:34 Subversion 1.5.4, apr 1.2.12 apr-utils 1.2.12 berkeley db 4.4.20 neon 0.28.3 OpenSSL 0.9.8i 15 Sep 2008 zlib 1.2.3) When connecting to this repository, I am getting "Error: Could not obtain the list of SASL mechanisms". I think I followed the instructions in the svn book : http://svnbook.red-bean.com/en/1.5/svn.serverconfig.svnserve.html#svn.serve…, although the instructions are very sparse. I'm not quite sure hwo sasl is supposed to know to use the svn.conf file to authenticate with svnserve. I am running svnserve from xinetd. Here is my /etc/xinetd.d/svnserve.conf # default: on # Subversion server service svnserve { socket_type = stream protocol = tcp user = root wait = no disable = no server = /usr/bin/svnserve server_args = -i -r /svn port = 3690 } Not quite sure why this isn't working. Does anyone have any ideas? Russ

1 1

cpu load monitoring
by Dave Stevens 23 Jan '09

23 Jan '09

Hi, I have a server running Centos 5.2 and am implementing a GIS mapserver app. I have some sample logs from another implementation that give me an idea of bandwidth requirements but I would like to check the cpu load. I can not be at the server during the test and am interested in knowing if there is logging of cpu load available. Anyone have experience with this? Recommendations? Dave -- Canada must refuse to be entangled in any more wars fought to make the world safe for capitalism. -- The Regina Manifesto, 1933

8 8

Re: [CentOS] Antivirus for CentOS? (yuck!)
by David G. Miller 23 Jan '09

23 Jan '09

Stephen John Smoogen <smooge(a)gmail.com> wrote: > On Thu, Jan 22, 2009 at 12:42 PM, David G. Miller <dave(a)davenjudy.org> wrote: > >> > Amos Shapira <amos.shapira(a)gmail.com> wrote: >> > >> >>> >> Hi All, >>> >> >>> >> Yes, I know, it's really really embarrassing to have to ask but I'm >>> >> being pushed to the wall with PCI DSS Compliance procedure >>> >> (http://en.wikipedia.org/wiki/PCI_DSS) and have to either justify why >>> >> we don't need to install an anti-virus or find an anti-virus to run on >>> >> our CentOS 5 servers. >>> >> >>> >> Whatever I do - it needs to be convincing enough to make the PCI >>> >> compliance guy tick the box. >>> <SNIP> >> > After reading all of the other replies (including the ones that pointed >> > out that the PCI DSS requirement had changed the terminology from >> > "virus" to "malware"), why not claim you are meeting the requirement by >> > doing something useful like running chkrootkit or rkhunter on a regular >> > basis? That way you would be scanning the systems for the only malware >> > known to actually pose a threat to a Linux box. It may be a low >> > probability of infection (as others have pointed out) but should satisfy >> > the auditor and hopefully will just be a low cost exercise in futility >> > as long as reasonable security policies are followed. >> > > Any tool will require the need to have a risk assessment against it. > What is the liklihood of it finding malware? How much is updated and > how does it compare to other tools. These will be questions that will > need to be available for auditors to know you did your due-diligence > on selecting a tool. Answering those questions would provide the arguments for running a root kit scanner instead of anti-virus software. That is, the risk of malware affecting the systems in question is low with near zero likelihood that a true virus will cause a problem but with the possibility that a rootkit could compromise the systems. Chkrootkit and rkhunter are arguably the best tools for finding a root kit. The programs are updated whenever a new threat is identified. Obviously, the OP would need more than my say so as back up for these assertions. Said back up would also make the case that scanning for non-existent threats (Linux viruses) would make no sense while scanning for a real threat makes the most sense. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

2 1

OT: Managing change control in servers, LDAP, firewalls and switches question
by Erick Perez 23 Jan '09

23 Jan '09

Hi, being an off-topic questions with so many vendors involved I had no definitive place to go to ask but here. So maybe some of the list members have ideas in mind. Currently we manage several switches,firewalls and MS LDAP and Centos OpenLDAP installations. We are looking for a "man in the middle" or "framework" to manage change on our network devices and LDAP-based servers. So far, using Quest ActiveRoles/Intrust has filled the part of LDAP, where administrators log into ActiveRoles/Intrust system, generate changes (delete OU, users, change passwords, etc) then the request has to be approved by a staff member in Activeroles/intrust. When the approval is sent to the system, the ActiveRoles/Intrust (and not the sysadmin) logs into the LDAP systems and perform the changes. This has proven useful in tracking changes (who did what, when, who approved it). We are looking into a similar solution (Quest Software does not have that for devices) to perform change and control on the routers, switches and firewalls. Maybe someone can also point me to a mailing list where i can ask the same question? thanks, -- ------------------------------------------------------------ Erick Perez Cel +(507) 6675-5083 ------------------------------------------------------------

4 4

SquirrelMail Sending Under Wrong Username
by John Hinton 23 Jan '09

23 Jan '09

CentOS team... as is already bug reported and marked solved... as we await the upstream repair for this. It was reported that this was happening on CentOS 5. You likely already know, but it also happens on CentOS 4. For those unaware. It seems that SquirrelMail has an issue which allows mail to be sent out from one user on the system and it uses the from address of another user on the system. Apparently, both users need to be logged into SM at the same time. My client reported that when he sent the affected message, he received a connection lost notice. He logged in again, stated that the email was in fact sent. The recipient of that email asked what was up with the odd from address. Looking at the headers from that message, they do in fact show adifferentusername(a)thisparticularservername.com. This is about the most embarrassing thing that's ever happened with my servers. Obviously the affected user is not feeling very secure. It does invite the recipient to reply to the wrong address which could be bad on so many levels (imagine having a few local law firms hosted on the same server?). I view this as a horrid security issue. If maybe the CentOS team might be so kind as to push the SquirrelMail update to the front when it's ready, that would be greatly appreciated. John Hinton

3 2

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