Discuss

discuss@lists.centos.org

34758 discussions

password aging for openldap in Centos 4.5
by tblader 09 Jan '08

09 Jan '08

Anyone have password aging working in Openldap 2.2.13-7 on Centos? The system continues to prompt for a new password regardless of whether it's been changed or not. Thanks -- Flambeau Inc. Technology Center - Baraboo, WI Email : tblader(a)flambeau.com Keyserver: http://pgp.mit.edu KeyID: 0x00E9EC2C

4 3

kbs-CentOS-testing rsyslog unsigned, yum won't update it on 5.1
by William L. Maltby 09 Jan '08

09 Jan '08

As the subject says. Just an FYI. -- Bill

2 1

max mount count incovenient
by Linux Man 09 Jan '08

09 Jan '08

Hello group I added a new partition in fstab, and works without a problem. I used mkfs.ext3 to create the partition. My problem is that every 26 boots, the system tells that the partition have no been checked since 26 systems boots, ant start to check my new partition. This is a lot of time consuming, and always is in a bad time. There some way to do the check in a controlled time? i.e. do it the check before 26 system boot, when the time is no problem. Thanks a lot Best regards

5 6

Hostap
by robert boardman 08 Jan '08

08 Jan '08

Hi All Is there an easy way to add hostap support to centos 5 without recompiling the kernel, although I have a prism 2.5 card the stock install doesn't seem the allow this to be setup as an AP thanks in advance for the advice Robb

1 0

Error logs where?
by Christopher E 08 Jan '08

08 Jan '08

Hello all, does any one know where the error log for the server would be in what dir? Thanks Christopher

4 3

Fwd: Securing Linux laptops
by Robert Moskowitz 08 Jan '08

08 Jan '08

http://www.linux.com/feature/123579 Feature: Wireless & Mobile Securing Linux laptops By Rick Cook on January 07, 2008 (9:00:00 PM) Print Comments Laptop and notebooks are being stolen at an ever-increasing rate. In 2004, Safeware Insurance which sells computer insurance, estimated 600,000 laptop and notebooks a year were being stolen. In 2006 an estimated 750,000 were being swiped, according to Absolute Software a company that makes computer tracking products -- and does not support Linux. LoJack For Laptops, another computer tracing company -- which also does not support Linux -- says FBI statistics show 2 million laptop and notebook computers were stolen in the US in a recent year. While the figures may not agree in detail, they all show that laptop and notebook theft is a major problem -- and if you're not careful, your Linux laptop might be next. ...... For the rest see the URL. So what options do we have for encrypting partitions. Can you encrypt a LVM that has /home on it (or just the ext3 in the LVM)? What about /boot on a USB dongle. I actually think I know how to do this at install with Disk Druid. But can you unmount /boot after booting up (don't want to walk around with the dongle on the system, wear it around my neck on a lanyard).

5 4

centos 5.1 kernel dump
by Jerry Geis 08 Jan '08

08 Jan '08

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll" option) Jan 8 05:20:00 localhost kernel: Jan 8 05:20:00 localhost kernel: Call Trace: Jan 8 05:20:00 localhost kernel: <IRQ> [<ffffffff800b5d77>] __report_bad_irq+0x30/0x7d Jan 8 05:20:00 localhost kernel: [<ffffffff800b5faa>] note_interrupt+0x1e6/0x227 Jan 8 05:20:00 localhost kernel: [<ffffffff800b54bc>] __do_IRQ+0xc7/0x105 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a3bd>] do_IRQ+0xe7/0xf5 Jan 8 05:20:00 localhost kernel: [<ffffffff8005b615>] ret_from_intr+0x0/0xa Jan 8 05:20:00 localhost kernel: [<ffffffff80011cba>] __do_softirq+0x53/0xd5 Jan 8 05:20:00 localhost kernel: [<ffffffff801515dd>] end_msi_irq_wo_maskbit+0x9/0x16 Jan 8 05:20:00 localhost kernel: [<ffffffff8005c2fc>] call_softirq+0x1c/0x28 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a53a>] do_softirq+0x2c/0x85 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a3c2>] do_IRQ+0xec/0xf5 Jan 8 05:20:00 localhost kernel: [<ffffffff8005b615>] ret_from_intr+0x0/0xa Jan 8 05:20:00 localhost kernel: <EOI> [<ffffffff8000cb74>] bit_waitqueue+0x3c/0xb4 Jan 8 05:20:00 localhost kernel: [<ffffffff8002ce23>] wake_up_bit+0x11/0x22 Jan 8 05:20:00 localhost kernel: [<ffffffff880328ef>] :jbd:do_get_write_access+0x137/0x527 Jan 8 05:20:01 localhost kernel: [<ffffffff800192e9>] __getblk+0x25/0x22c Jan 8 05:20:01 localhost kernel: [<ffffffff88032d01>] :jbd:journal_get_write_access+0x22/0x33 Jan 8 05:20:01 localhost kernel: [<ffffffff8804dc75>] :ext3:ext3_reserve_inode_write+0x38/0x90 Jan 8 05:20:01 localhost kernel: [<ffffffff8804dcee>] :ext3:ext3_mark_inode_dirty+0x21/0x3c Jan 8 05:20:01 localhost kernel: [<ffffffff88050b14>] :ext3:ext3_dirty_inode+0x63/0x7b Jan 8 05:20:01 localhost kernel: [<ffffffff8001349c>] __mark_inode_dirty+0x29/0x16e Jan 8 05:20:01 localhost kernel: [<ffffffff8804b5f5>] :ext3:ext3_new_blocks+0x567/0x693 Jan 8 05:20:01 localhost kernel: [<ffffffff80025273>] __bread+0x6/0x81 Jan 8 05:20:01 localhost kernel: [<ffffffff8804e46b>] :ext3:ext3_get_blocks_handle+0x43a/0x9f1 Jan 8 05:20:01 localhost kernel: [<ffffffff88032ca8>] :jbd:do_get_write_access+0x4f0/0x527 Jan 8 05:20:01 localhost kernel: [<ffffffff8804ed42>] :ext3:ext3_get_block+0xbe/0xe3 Jan 8 05:20:01 localhost kernel: [<ffffffff8000e1b3>] __block_prepare_write+0x1b6/0x4a0 Jan 8 05:20:01 localhost kernel: [<ffffffff8804ec84>] :ext3:ext3_get_block+0x0/0xe3 Jan 8 05:20:01 localhost kernel: [<ffffffff8003c1d4>] block_prepare_write+0x1a/0x25 Jan 8 05:20:01 localhost kernel: [<ffffffff88050260>] :ext3:ext3_prepare_write+0xaf/0x17b Jan 8 05:20:01 localhost kernel: [<ffffffff8000f9cb>] generic_file_buffered_write+0x25a/0x6d8 Jan 8 05:20:01 localhost kernel: [<ffffffff8000cca5>] file_read_actor+0xb9/0x154 Jan 8 05:20:01 localhost kernel: [<ffffffff8000ddd9>] current_fs_time+0x3b/0x40 Jan 8 05:20:01 localhost kernel: [<ffffffff8000cbec>] file_read_actor+0x0/0x154 Jan 8 05:20:01 localhost kernel: [<ffffffff80015dc6>] __generic_file_aio_write_nolock+0x36c/0x3b8 Jan 8 05:20:01 localhost kernel: [<ffffffff8002134b>] generic_file_aio_write+0x65/0xc1 Jan 8 05:20:01 localhost kernel: [<ffffffff8804c192>] :ext3:ext3_file_write+0x16/0x91 Jan 8 05:20:01 localhost kernel: [<ffffffff80017958>] do_sync_write+0xc7/0x104 Jan 8 05:20:01 localhost kernel: [<ffffffff8009b492>] autoremove_wake_function+0x0/0x2e Jan 8 05:20:01 localhost kernel: [<ffffffff8000cbec>] file_read_actor+0x0/0x154 Jan 8 05:20:01 localhost kernel: [<ffffffff800161d8>] vfs_write+0xce/0x174 Jan 8 05:20:01 localhost kernel: [<ffffffff80016a8d>] sys_write+0x2d/0x6e Jan 8 05:20:01 localhost kernel: [<ffffffff80016aa5>] sys_write+0x45/0x6e Jan 8 05:20:01 localhost kernel: [<ffffffff8005b28d>] tracesys+0xd5/0xe0 Jan 8 05:20:01 localhost kernel: Jan 8 05:20:01 localhost kernel: handlers: Jan 8 05:20:01 localhost kernel: [<ffffffff801dadc4>] (usb_hcd_irq+0x0/0x55) Jan 8 05:20:01 localhost kernel: Disabling IRQ #169

3 3

tar bug in CentOS 4.6?
by David G. Miller 08 Jan '08

08 Jan '08

Since upgrading my server from CentOS 4.5 to 4.6 I've been getting the following error from amanda backups: mutilate /home lev 1 FAILED [compress got signal 11, /bin/tar got signal 13] I was away from the house for most of the end of December and had a couple of other issues that came up that could have been related but apparently weren't (why is it that several things all go wrong at once?). After getting these other issues resolved I was still getting the above error. I tried running the following command as root: /bin/tar -X /etc/amanda/exclude-list/exclude.txt -cvf - /home | gzip -v -c > /share/dave/Home.tar.gz Initially tar would die while attempting to back up one of IMAP folders that had quite a few fairly large e-mails (some pictures my brother had sent). I removed the larger e-mails and tar proceeded past the IMAP folder that had been the problem only to die later: ... /home/judy/Judy's Stuff/School/ /home/judy/Judy's Stuff/School/2007 Spring/ /home/judy/Judy's Stuff/School/2007 Spring/Mynametemplate.ppt /home/judy/Judy's Stuff/School/2007 Spring/MyNameSamples.doc /home/judy/Judy's Stuff/School/2007 Spring/Myname105.ppt /home/judy/Judy's Stuff/School/2007 Spring/TYP Types.doc /home/judy/Judy's Stuff/School/2007 Spring/Photoshop_CS2.exe Segmentation fault The copy of PhotoShop is the trial version that my wife had downloaded about a year ago for a class she was taking. This directory has been getting backed up at least every thirty days since then given my tape rotation. If I remove the PhotoShop_CS2.exe file, the backup completes normally. So, is this a tar bug (doesn't like big files now) or is there some other issue like available shared memory that's causing the problem? Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

3 2

Problem with CentOS 5.1/xen/RTL8110
by Chris Gow 08 Jan '08

08 Jan '08

Hello: I'm having issues with my CentOS 5.1/Xen installation. If I run the xen-bridge, I seem to get flaky ethernet. By flaky I mean everything seems fine from the host machine, but if I attempt to contact the host machine from another remote machine (eg. my laptop which is on the same subnet as the xen machine, separated by 10 ft of cable and a router) I either get extremely high ping times or Destination Host Unreachable. Ditto with ssh. I've disabled the firewall and it does not make a difference. If I stop the xen-bridge (/etc/xen/scripts/network-bridge stop) then I get what I would consider normal network access to the xen machine. Hardware: Gigabyte GA-G33M-S2H MB (Realtek R8110SC onboard nic) OS: CentOS 5.1 64bit Xen I installed CentOS last night with the Xen kernel, the stock kernel did not support my nic which I was aware of. So I downloaded the r1000 source rpm from the centos wiki, built and installed it. Once I did that the card was detected (an ifconfig would actually display eth0), but it would never get an IP address (the xen machine is configured for dhcp at the moment). Today, I installed the non-xen kernel, applied the non-xen r1000 kernel module and the onboard nic was found and working. I then grabbed the updates from centos, saw that there were some kernel updates, applied the r1000 kernel modules again, restarted and (the non-xen kernel) eth0 was still happy. Good. Restarted again, but booted into the xen kernel, eth0 was still happy. eth0 would get an IP address, and was able to see the outside world. However, the outside world (eg. my laptop) could not see the xen machine or it could inconsistently. That is, ping times would be extremely high (on the order of 2+ seconds) or I would get Destination Host Unreachable errors. Trying to connect via ssh would also be sporadic. Thinking it might be firewall related, I disabled the firewall. There was no change in behaviour. I then disabled the xen-bridge and was able to ping with reasonable numbers (<200ms) and connect via ssh. Just to note though, after I stopped the bridge I immediately tried to connect via ssh/ping and did not get through, so I ran service iptables stop (again) and then was able to get correct network access. I'm not sure if stopping iptables again did anything (I doubt) or I did not leave enough time from stopping the bridge to letting everything get reconfigured. I'm not sure what the problem is or how exactly to troubleshoot it. The NIC is slightly different than the one specified in the CentOS wiki (the wiki mentions RTL8110 and RTL8169SC and mine is a RTL8110SC) but I'm not familiar enough with the devices to know how much of a big deal that is, if any. Also, just to be clear, the problem is other physical machines have a difficult time accessing the xen host pc when the xen-bridge is running. I have not gotten as far as creating a VM yet. Any assistance would be great. thanks -- chris

5 5

yum update download only?
by Kenneth Porter 08 Jan '08

08 Jan '08

Googling for this feature, I saw reports from the yum developer that it wasn't yet implemented. This was in mailing list posts from a year or more ago. Did it ever make it into the yum code? I want to start downloading the updates for a server going from 5.0 to 5.1 and then do the actual installation once I'm on site. I don't want to have to wait around while there for the download to proceed. I'd rather have all the packages ready in the yum cache when I get there.

4 5

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