RE: [CentOS] Locating the broken links
Hi, Any pretty way to find broken links on the entire filesystem would be welcome however. I have a script available for this: #!/bin/bash # command line parameter would be the directory to search for i in ` find $1 -type l `; do # feststellen, ob der link noch gueltig ist oder nicht file $i | grep -q broken if [ $? -eq 0 ] ; then echo Broken link $i fi done exit Christian Volker Technical Support Engineer -- Parnell House, Barrack Square, Ballincollig, Co. Cork, Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] Re: rsync and swapping
Yohoo! Rsync's main benefit is on backups of changed files. dumping to a new destination every time makes rsync less efficient than just about every other option. Now if you made the new directory, and hardlinked the old stuff to the new directory, then rsync would shine. That's what rsnapshot is designed for. It uses rsync to sync the files to a backup destination and hardlinks any existing file, so you can go back to any level you like. Christian ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] Vmware Server on Centos 5.1
Yohoo! Has any one done that yet, upgraded his vmware hosts with Centos/RHEL 5.0 to 5.1 ? I'm running VMware Server 1.0.4 on CentOS5. My yum is updating weekly so meanwhile I have a 5.1. Still working fine. Of course, when you reboot you have to recompile the VMware modules (just start vmware-config.pl) after the reboot before the VMware Server will start. Looking forward to hearing from you. Christian Volker Technical Support Engineer Ballincollig, Co. Cork Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] smartd.conf get overridden
Yohoo! the first three lines of my /etc/smartd.conf are: # *SMARTD*AUTOGENERATED* /etc/smartd.conf # Remove the line above if you have edited the file and you do not want # it to be overwritten on the next smartd startup. Yes, that's it! I haven understood what the init script is checking for. Fixed it for me now. THX! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] Re: CentOS 5 and removing sendmail
Yohoo! # rpm -e sendmail error: Failed dependencies: rpm -e sendmail --nodeps No --- Don't --- Install another MTA before you try to remove sendmail. Where's the difference? Christian Volker Technical Support Engineer Ballincollig, Co. Cork Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] New machine dying on boot.... - CPU 0 not enough memory for domain -
Yohoo! From a first guess I would think the memory isnt' balanced right. On a NUMA system (like the Opterons) it is strongly recommended to have all CPUs with the same amount of local memory. So open the case and check if the CPU0 really has some memory in his slots. Christian Volker Technical Support Engineer -- Parnell House, Barrack Square, Ballincollig, Co. Cork, Ireland -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Plemons Sent: 13 November 2007 19:37 To: centos@centos.org Subject: [CentOS] New machine dying on boot - CPU 0 not enough memory for domain - I am playing with a new machine I just got in and it is dying on boot... I'm wondering if it is to much machine for Centos to run.. It is a Generic machine using a Tyan Thunder motherboard running (8) eight dual core AMD 855 cpu's with 128 gig of ram, not 128 meg, but 128 gig of ram. (2) SCSI 146 Seagate Drives. ATI Graphics built onto the board. The error I'm seeing is on loading the Kernel, I get a message that says CPU 0 not enough memory for domain I'm lost with 128 gig of ram I'd think there is plenty of memory... The load is a fresh install ( today ) of Centos 5 - x86_64 version Used the defaults on all of the items it is vanilla as can be, yet it chokes and dies... As for the machine, it is a new machine that I just picked up, I'm loading Centos to make sure it is working correctly... thanks, john ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS5 and ipw2200
Hi all! I tried to use CentOS5 on an IBM Thinkpad R52 which has an Intel PRO/Wireless 2915ABG Mini-PCI Adapter installed. I downloaded the firmware from the DAG-Repo (afaik 3.0.0) and added a alias eth1 ipw2200 to modules.conf. After the module was loaded successfully (including the firmware) I was able to configure the card. For simplicity I didn't use any encryption. My access point as well is not using any encryption. I tried to use DHCP, but the card didn't get assigned to any IP address. So I used the manual configuration which seemed to work fine during startup. But unfortunately not network connection could be made. So no ICMP ping packets where reaching the destination. Using the iwconfig command I could see my SSID from the access point. Playing around with some values didn't have any success. So I tried using FC8- and it worked fine with fixed address settings. As well as OpenSuSE 10.2. Anyone an idea what's going wrong here? Christian Volker Technical Support Engineer -- Parnell House, Barrack Square, Ballincollig, Co. Cork, Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS5 and ipw2200
Yohoo! I tried to use CentOS5 on an IBM Thinkpad R52 which has an Intel PRO/Wireless 2915ABG Mini-PCI Adapter installed. I downloaded the firmware from the DAG-Repo (afaik 3.0.0) and added a alias eth1 ipw2200 to modules.conf. After the module was loaded successfully (including the firmware) I was able to configure the card. can you compare the iwconfig output on centos5 and FC8 ? Not in the next two weeks. Sorry for that. As far as I remember it was the same. And I compared the values with the ones stored in /etc/sysconfig/networking/...ifup-eth1 Your was already installed when you installed centos5 ? And for FC8 ? What do you mean? If the card was already installed? Yes it was. And on all tests it was a fresh installation. Can you try to install a FC8 kernel, if you don't suffer dependency problem ? (or with a FC7 kernel) I can try this as well, but not within the next two weeks. So you're assuming it's related to the kernel? On the OpenSuSE it's kernel 2.6.18.8-0.7-default, which seems to be nearly the same as on CentOS5 2.6.18-8.1.15.el5. So I don't believe it will be fixed with a newer kernel. If static IP is working, are you sure your DHCP is working on the wireless side ? Yes, I am sure. Another (Windows) laptop is working fine with DHCP in the same WLAN. Looking forward to hearing from you. Christian Volker Technical Support Engineer Ballincollig, Co. Cork Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS5 and ipw2200
Yohoo! I tried to use DHCP, but the card didn't get assigned to any IP address. So I used the manual configuration which seemed to work fine during startup. But unfortunately not network connection could be made. So no ICMP ping packets where reaching the destination. I have had a similar experience. After your interface starts, check to see if dhclient is running. It seems that for some reason, even though I have BOOTPROTO=dhcp in the interface configuration file, it doesn't get an address, but if I run dhclient eth1 it gets an address immediately. Even when I configure it manually, I don't get any connectivity. So it doesn't seem to be related to DHCP here. But it could be related to the DHCP issue I'm seeing on FC8 and OpenSuSE10.2 Thanks for the hint. So you have an ipw2200 running in CentOS5 without any issues? How did you do this? ;) Looking forward to hearing from you. Christian Volker Technical Support Engineer Ballincollig, Co. Cork Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] rsync bug with --relative and --delete fixed in CentOS5?
Yohoo! I'm using rsnapshot-1.3.0-1.el5.rf (from DAG) and rsync-2.6.9-1.el5.rf (from CentOS5) together. Rsnapshot now starts every task with the --relative switch. Without this switch it will backup all subsequent folders (like /proc and so on) which isn't desired. So I can't omit the --relative. But there was a bug for rsync prior to 2.6.9 that it won't delete files from the destination directory when --relative and --delete are used together. See at http://samba.anu.edu.au/ftp/rsync/rsync-2.6.9-NEWS for this. Now I figured out that this bug is fixed in FedoraCore5. See http://www.redhat.com/archives/fedora-package-announce/2007-February/msg00105 .html The version there is rsync-2.6.9-1.FC5.1. In CentOS5 I have rsync-2.6.9-1.el5.rf Now my question is if this bug is fixed in CentOS5/ RHEL5? If not, is there something scheduled to fix it or should I build the rsync package from the source of the FC5 tree? Thanks! Christian Volker Technical Support Engineer -- Parnell House, Barrack Square, Ballincollig, Co. Cork, Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] rsync bug with --relative and --delete fixed in CentOS5?
Yohoo! In CentOS5 I have rsync-2.6.9-1.el5.rf Now my question is if this bug is fixed in CentOS5/ RHEL5? I am not sure if it is fixed in CentOS-5 or not, but that is not relevant since you are NOT using the CentOS-5 rsync. rsync-2.6.9-1.el5.rf ... the rf stands for RPMForge .. so, that is the RPMForge version of rsync. rsync-2.6.8-3.1 == that is the version of rsync from CentOS-5. You're right! I wasn't aware that this is the version from RPMForge. On the source server there was still the CentOS one 2.6.8 WITH the bug. So the solution is: Original rsync-2.6.8-3.1 has still this bug. DAG rsync-2.6.9-1.el5.rf has fixed this bug. With the newer version on both sides it now works fine! Thanks for the hint. Christian Volker Technical Support Engineer Ballincollig, Co. Cork Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
