Discuss

discuss@lists.centos.org

34758 discussions

Centos 4.4: Support for Dell PowerEdge 830 CERC 6-Channel SATA RAID Controller
by Erick Perez 14 Sep '06

14 Sep '06

Does Centos/RHEL 4.4 supports the CERC 6-Channel SATA RAID Controller that comes with the Dell PowerEdge 830 Tower Server? -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 ------------------------------------------------------------

2 2

RE: [CentOS] backup server..
by Sebastien Tremblay 14 Sep '06

14 Sep '06

> Well to answer this point, there is yum's "group install" feature. > You can see the available groups and their status with: > # yum grouplist | less > And to install X it would be something like: > # yum groupinstall "GNOME Desktop Environment" > done deal. > d Gee... Never of that one!! I sure will give that group install a look! Cheers! Seb. _____________________________________________________________________ This message and any attachments are confidential and are solely intended for the use of the addressee(s). If you are not the intended recipient please contact the sender by reply email. Please also disregard the contents of this email and delete and destroy any copies immediately. CMPMedica Australia Pty Ltd does not accept liability for the views expressed in this email or for the consequences of any computer viruses that may be transmitted with this email. Also subject to copyright, no part of this message should be reproduced or transmitted without written consent.

1 0

CDRW and DVDRW support in Centos 4.4
by Erick Perez 14 Sep '06

14 Sep '06

HI, I configured a minimum install on Centos 4.4 and then added postfix+dovecot+openwebmail I want to use Mondo Rescue (disaster recovery solution) and the program needs CD-R/RW and DVD-+R/RW support. What are the packages required to install via yum to provide support for the creation of CD/DVD? I know mkisofs and cdrecord are two of them, what others? thanks, -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 ------------------------------------------------------------

2 1

sun java install?
by Les Mikesell 14 Sep '06

14 Sep '06

Has anyone installed the 1.4.x version of java the jpackage way recently? It looks like sun only has j2sdk-1_4_12 but the jpackage java-1.4.2-sun-compat package wants 4.2_10. -- Les Mikesell lesmikesell(a)gmail.com

1 0

network prob on Centos 4.4/HP DL320 G2
by fredex 14 Sep '06

14 Sep '06

Hi! I've installed Centos 4.4 on a machine at work (it's a HP Proliant DL-320 G2 rackmout server that serves my desktop). In recent days (Centos 4.4 has only been installed for a little over a week), like, since Wed or Thu last week, every time I reboot Kudzu wants to remove the network adaptors then reinstall them and breaks the network. I've gone to the point of disabling one of the network ports in the BIOS (since I only use one of them anyway), and at first it worked when I rebooted, after doing the obligatory net configuration. Then the next time I rebooted Kudzu again wanted to remove and reinstall the network and it again didn't work after the reboot. Today I had to reboot again (because X went nutso and I lost my mouse pointer--I know, a reboot is overkill, don't remind me) and once again it broke the network when it rebooted. The network config GUI applet could not activate the net, it kept complaining that the MAC address of the adapter was not the one it expected. I removed (as the previous time) all the NETWORK items from /etc/sysconfig/hwconf and rebooted again, after which it came up. But I fully expect it to be broken yet again when I reboot next time. This machine ran RHEL WS 2.1 for something like 3 years and never had this kind of trouble, even with both ports enabled in the BIOS. I always used the tg3 driver that came with Linux, not the driver that HP offers. The only RPM I've installed that I got from HP is the one that installs "hpasm", because that's the one that turns the fans from "screaming jet engine" into "low roar". (this system contains a dozen or so small fans, all of which rotate at a gazillion rpm, all not quite the same speed, so you get a dozen slightly different pitches, causing heterodyning and the resultant throbbing along with the screaming if you don't use the hpasm module.) Suggestions please? -- ------------------------------------------------------------------------------- .---- Fred Smith / ( /__ ,__. __ __ / __ : / / / / /__) / / /__) .+' Home: fredex(a)fcshome.stoneham.ma.us / / (__ (___ (__(_ (___ / :__ 781-438-5471 -------------------------------- Jude 1:24,25 ---------------------------------

3 3

RE: [CentOS] Lingering dhclient issue
by Justin Randall 14 Sep '06

14 Sep '06

>Yes, it would. My question was what is the recommended process to >switch an interface from DHCP to STATIC so that the dhclient process >automatically gets killed. Doing an "ifdown eth0", editing the >configuration file, and then doing an "ifup eth0" left this lingering >dhclient process around. If you're looking for a one command solution after making the required configuration changes, using the "service network restart" is likely your best bet. If you don't want to restart the entire network (which can cause service interuption depending on what is being serviced over the network), simply carrying out the steps you originally outlined while killing the dhclient process acting on the interface is probably the best approach since there is no association between ifconfig and dhclient. Regards, Justin. -----Original Message----- From: Alfred von Campe [mailto:alfred@110.net] Sent: Wed 9/13/2006 7:27 PM To: CentOS mailing list Cc: Subject: Re: [CentOS] Lingering dhclient issue On Sep 13, 2006, at 17:07, Johnny Hughes wrote: > I do: > > service network restart I'll remember this for next time. If I get a chance, I will also test this to see if the dhclient process indeed goes away. On Sep 13, 2006, at 18:29, Justin Randall wrote: > Unless this device is going to be switching from DCHP to static > frequently, wouldn't simply killing the dhclient process be > sufficient? Yes, it would. My question was what is the recommended process to switch an interface from DHCP to STATIC so that the dhclient process automatically gets killed. Doing an "ifdown eth0", editing the configuration file, and then doing an "ifup eth0" left this lingering dhclient process around. Alfred _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

Disabling IPv6 in Centos 4.x Experiences
by Erick Perez 13 Sep '06

13 Sep '06

Hi there, While I was looking "how to disable ipv6 under centos" I have found a gazzillion pages about how to do it and some of then even list things that i am not sure where they came from, so for the record I list most of them here in case someone else need them. Some of the methods involved the direct modification of system scripts, and I am against that so I wont list them here (removing the entire section of ipv6 calls in IFUP is not a good idea). How to disable ipv6 support in Centos 4.x Pick any method, a combo or all of them Method 1, add the line: alias net-pf-10 off to the /etc/modprobe.conf Method 2 Add to /etc/sysconfig/network file: NOZEROCONF=yes # Bonus: Disable the ugly generation of 169.254 zeroconf networks. NETWORKING_IPV6=no Note about method 2. I must mention the fact that I actually READ the entire ifup script and dependencies and I found that it calls at line 361: # if [ "${NETWORKING_IPV6}" = "yes" ]; then # /etc/sysconfig/network-scripts/ifup-ipv6 ${CONFIG} However adding the NETWORKING_IPV6=NO has no effect whatsoever because even after a reboot the interfaces continue to load an ipv6 address. BTW it does the same for zeroconf and doesn`t work either. Method 3: /etc/sysconfig/network-scripts/ifcfg-XXXXX file; IPV6INIT=no So pick your best method or a combo and let us know which one worked for you: In my case Centos 4.3 2.6.9-34.EL i386 with a pair of 3COM 3c905CX lan boards did not responded to Method 1 and 2 and 3. So I'm still battling with this ipv6 thing. Let me know your comments. Cheers, -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 ------------------------------------------------------------

13 25

RE: [CentOS] Lingering dhclient issue
by Justin Randall 13 Sep '06

13 Sep '06

> My question is, what could I have done to avoid this (other than >killing the dhclient process)? Is there a better way to reconfigure >an interface to use a static address? I am not interested in >solutions that involve using a GUI (i.e., only command line solutions). Unless this device is going to be switching from DCHP to static frequently, wouldn't simply killing the dhclient process be sufficient? If not, you could always simply write a shell function for ifconfig (if you're using bash, ksh or sh) that checks for an associated dhclient process when and interface is "down"'d and kills the associated dhclient process. Hope this helps, Justin. -----Original Message----- From: Alfred von Campe [mailto:alfred@110.net] Sent: Wednesday, September 13, 2006 2:06 PM To: CentOS mailing list Subject: [CentOS] Lingering dhclient issue I recently reconfigured some CentOS 4.3 systems that were using DHCP to use static IP addresses. At the same time, the systems were moved to a new VLAN. Here is the approximate sequence of events that took place: 1. ifdown eth0 2. edit /etc/sysconfig/network-scripts/ifcfg-eth0 with static IP address 3. wait for network folks to reconfigure switch 4. ifup eth0 I may have reversed steps 1 and 2 on some of the systems. The problem was that the dhclient process didn't go away, and kept renewing the old lease. Our DHCP server is configured to contact the DNS server and update the entry for each host it serves. So the DNS entries for these systems were pointing to the old address in the old VLAN. The eth0 interface itself just kept the static IP address for which it was configured. It took me a while to figure out what was going on. My question is, what could I have done to avoid this (other than killing the dhclient process)? Is there a better way to reconfigure an interface to use a static address? I am not interested in solutions that involve using a GUI (i.e., only command line solutions). Thanks, Alfred _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

Revisited - No fullscreen on FreeNX
by Jay Leafey 13 Sep '06

13 Sep '06

This topic came up some time back and I pretty much ignored it, but the "itch" came back to find out why. Searching through the FreeNX/knx list came up with the reason sessions did not come up full-screen even though the session definition was set to fullscreen. Apparently there is an oversight in /usr/bin/nxnode, the script is never retrieving the fullscreen flag from the parameters passed from the client. This is the case even in freenx-0.5.0-9.c4, the current version for CentOS 4. Here's a quick patch against the freenx-0.5.0-9.c4 version of /usr/bin/nxnode that resolves this issue: ***PATCH START*** --- nxnode.save 2006-09-13 12:01:31.000000000 -0500 +++ nxnode 2006-09-13 12:02:08.000000000 -0500 @@ -626,6 +626,7 @@ imagecompressionmethod=$(getparam imagecompressionmethod) imagecompressionlevel=$(getparam imagecompressionlevel) geometry=$(getparam geometry) + fullscreen=$(getparam fullscreen) keyboard=$(getparam keyboard) kbtype=$(getparam kbtype) media=$(getparam media) @@ -661,7 +662,6 @@ status=$(getparam status) host=$(getparam host) - fullscreen="" [ "$geometry" = "fullscreen" ] && fullscreen="1" [ "$EXPORT_USERIP" = "1" ] && export NXUSERIP="$userip" ***PATCH END*** After this patch, nxnode will respect the fullscreen flag if it is set in the configuration. Hope that helps! -- Jay Leafey - Memphis, TN jay.leafey(a)mindless.com

3 4

Re: [CentOS] benchmarking large RAID arrays
by David Thompson 13 Sep '06

13 Sep '06

"chrism(a)imntv.com" wrote: >I'm just wondering what folks are using to benchmark/tune large arrays >these days. I've always used bonnie with file sizes 2-3 times physical >RAM. Maybe there's a better way? For benchmarking a disk subsystem, I use iozone, with the kernel booted with mem=<nn> to create an artificially small buffer pool. Dave Thompson UW-Madison

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