Discuss

discuss@lists.centos.org

34753 discussions

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

13 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

CentOS-announce Digest, Vol 19, Issue 7
by centos-announce-request＠centos.org 13 Sep '06

13 Sep '06

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-2006:0666 Important CentOS 3 ia64 XFree86 - security update (Pasi Pirhonen) 2. CESA-2006:0663 Low CentOS 4 ia64 ncompress - security update (Pasi Pirhonen) 3. CESA-2006:0658 Low CentOS 4 ia64 wireshark - security update (Pasi Pirhonen) 4. CESA-2006:0665 Important CentOS 4 ia64 xorg-x11 - security update (Pasi Pirhonen) 5. CESA-2006:0663 Low CentOS 3 ia64 ncompress - security update (Pasi Pirhonen) 6. CESA-2006:0658 Low CentOS 3 ia64 wireshark - security update (Pasi Pirhonen) 7. CESA-2006:0665 Important CentOS 4 s390(x) xorg-x11 - security update (Pasi Pirhonen) 8. CESA-2006:0663 Low CentOS 4 s390(x) ncompress - security update (Pasi Pirhonen) 9. CESA-2006:0666 Important CentOS 3 s390(x) XFree86 - security update (Pasi Pirhonen) 10. CESA-2006:0663 Low CentOS 3 s390(x) ncompress - security update (Pasi Pirhonen) 11. CESA-2006:0658-01: Low CentOS 2 i386 wireshark security update (John Newbigin) 12. CESA-2006:0663-01: Low CentOS 2 i386 ncompress security update (John Newbigin) 13. CESA-2006:0666-01: Important CentOS 2 i386 XFree86 security update (John Newbigin) 14. CESA-2006:0658 Low CentOS 3 s390(x) wireshark - security update (Pasi Pirhonen) 15. CESA-2006:0665 Important CentOS 4 x86_64 xorg-x11 - security update (Johnny Hughes) 16. CESA-2006:0665 Important CentOS 4 i386 xorg-x11 - security update (Johnny Hughes) 17. CESA-2006:0663 Low CentOS 4 i386 ncompress - security update (Johnny Hughes) 18. CESA-2006:0663 Low CentOS 4 x86_64 ncompress - security update (Johnny Hughes) 19. CESA-2006:0658 Low CentOS 4 i386 wireshark - security update (Johnny Hughes) 20. CESA-2006:0658 Low CentOS 4 x86_64 wireshark - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Sep 2006 21:53:15 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2006:0666 Important CentOS 3 ia64 XFree86 - security update To: centos-announce(a)centos.org Message-ID: <20060912185315.GT17774(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2006:0666 https://rhn.redhat.com/errata/RHSA-2006-0666.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/XFree86-100dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-75dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-14-100dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-14-75dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-15-100dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-15-75dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-2-100dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-2-75dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-9-100dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-ISO8859-9-75dpi-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-Mesa-libGL-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-Mesa-libGLU-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-Xnest-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-Xvfb-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-base-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-cyrillic-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-devel-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-doc-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-font-utils-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-libs-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-libs-data-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-sdk-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-syriac-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-tools-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-truetype-fonts-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-twm-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-xauth-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-xdm-4.3.0-113.EL.ia64.rpm updates/ia64/RPMS/XFree86-xfs-4.3.0-113.EL.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

HAL Problems
by Christian Bolz 13 Sep '06

13 Sep '06

Hi, since the last few days my system crashs at startup of gdm (on system boot). If I choose runlevel 2, the system doesn't crash. I found out, that HAL is the problem. After disabling hal (chkconfig haldaemon --off) no crashes appear. The system freezes completly so I can't look into the logfiles. I removed an reinstalled hal already, but nothing changed. I tried older kernels releases and nothing changed. Any help would be nice! Regards, Christian

3 6

mailman update breaks my installation
by Oliver Schulze L. 13 Sep '06

13 Sep '06

Hi, I just updated to mailman-2.1.5.1-34.rhel4.5 and now the mailman web site is not working. I get this lines en apache error_log [Wed Sep 13 09:41:17 2006] [error] [client 200.85.40.xx] File does not exist: /usr/lib/mailman/cgi-bin/listinfo/listname listname is the name of the list. Anyone is having this problem? Thanks Oliver -- Oliver Schulze L. Get my e-mail after a captcha test in: http://tinymailto.com/oliver

1 1

procmail problem with postfix
by abhishek singh 13 Sep '06

13 Sep '06

Hi Friends I am configuring a mailserver , basically the working of this server is to fetchmail from remote server and we have one account that is catchall account and we are using procmail to distribute all mails properly to users, n i m building new server for my company but i m getting following error if i am sending mails from outside , if i am sending mail from my own domain then there is no problem procmail is working properly. plz help me out . i have remove my domain name by example . thanks This is the Postfix program at host internm.example.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the attached returned message. The Postfix program <root(a)localhost.example.com>: can't create user output file. Command output: procmail: Renaming bogus mailbox "/var/mail/nobody" info "/var/mail/BOGUS.nobody.T8r" procmail: Couldn't create "/var/mail/nobody" Final-Recipient: rfc822; root(a)localhost.dsconstructions.com Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; can\'t create user output file. Command output: procmail: Renaming bogus mailbox "/var/mail/nobody" info "/var/mail/BOGUS.nobody.T8r" procmail: Couldn\'t create "/var/mail/nobody" ---------- Forwarded message ---------- From: "Abhishek Singh" <abhishek.rhce(a)gmail.com> To: aksingh(a)dsconstructions.com Date: Wed, 13 Sep 2006 15:24:57 +0530 Subject: this is me v -- Abhishek Kumar Singh System Administrator D.S.C LTD. Mob: +91-9871563248 \n\n ",0] ); //--> Final-Recipient: rfc822; root(a)localhost.example.com Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; can't create user output file. Command output: procmail: Renaming bogus mailbox "/var/mail/nobody" info "/var/mail/BOGUS.nobody.T8r" procmail: Couldn't create "/var/mail/nobody" Abhishek Kr. Singh System Administrator DSC. LTD. Mob.No. +91-9871563248 --------------------------------- Find out what India is talking about on - Yahoo! Answers India Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW

2 3

Symantec Backup Exec 10d
by Evgeny Ivanov 12 Sep '06

12 Sep '06

Hi all, I am a CentOS newbie and I was wondering if I can get help regarding the Backup of CentOs with Backup Exec 10d Remtoe agents for Linux. have anyone tested this ? Evgeny

2 1

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