Discuss

discuss@lists.centos.org

34758 discussions

how to control sftp's user file folder
by Yang Yang 10 Mar '11

10 Mar '11

hi,i have a question want to ask if i add a user like: useradd test groupadd test -g www and how to control user test only can see and write only folder(like /home/htdocs/test,he can not see /home/htdocs or other folder) thanks very much

12 22

CentOS-announce Digest, Vol 73, Issue 3
by centos-announce-request＠centos.org 10 Mar '11

10 Mar '11

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-2011:0337 Important CentOS 4 x86_64 vsftpd - security update (Johnny Hughes) 2. CESA-2011:0337 Important CentOS 4 i386 vsftpd - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 10 Mar 2011 03:59:53 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2011:0337 Important CentOS 4 x86_64 vsftpd - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <4D78A119.2000301(a)centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory CESA-2011:0337 vsftpd security update for CentOS 4 x86_64: https://rhn.redhat.com/errata/RHSA-2011-0337.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: vsftpd-2.0.1-9.el4.x86_64.rpm src: vsftpd-2.0.1-9.el4.src.rpm

1 0

RHEL4 EOL
by Kwan Lowe 10 Mar '11

10 Mar '11

Just curious... CentOS4 lifetime tracks RHEL4 somewhat... Since RedHat has announced LTS (Long Term Support) for RHEL4, are there plans to extend the CentOS 4 support window?

4 6

Next3 (eg ext3 snapshots support) on OpenNode / CentOS 5 / RHEL 5 howto and rpms
by Andres Toomsalu 10 Mar '11

10 Mar '11

We have created an next3 and patched e2fsprogs OpenNode / CentOS 5 / RHEL 5 rpms - installable from opennode-test yum repo. Provided next3 kernel module is currently built against RHEL5 OpenVZ kernel used in OpenNode - so installing this next3 rpm package on your CentOS 5 or RHEL 5 host will install also OpenVZ patched RHEL5 kernel and newer e2fsprogs package. Installation and usage instructions are provided by this howto document: http://opennode.activesys.org/documentation/howtos/next3-snapshots/ There is also simple next3 snapshotting automation script available for use with cron - usage and download link provided in howto document referenced above. Regards, -- ---------------------------------------------- Andres Toomsalu, andres(a)active.ee

2 1

sata drives and controlers
by Michel Donais 10 Mar '11

10 Mar '11

I intend to replace fading SCSI drive by a SATA one. The motherboard is PCI and no SATA controller on board. So I need a SATA/PCI controller. Is there something wrong to do this kind of switch? Some told me that I won't be able to boot that drive. Loosing part of the SATA interface speed is not a decisive factor on this machine Is there are some prefered Linux SATA controller? Need experienced feedbacks. --- Michel Donais

4 5

Re: [CentOS] [Newbie] Reclaiming /boot space
by Simon Matter 10 Mar '11

10 Mar '11

> On Wed, Mar 9, 2011 at 10:12 AM, Simon Matter <simon.matter(a)invoca.ch> > wrote: >>> Yes...thank you for the suggestion...since that was the cause of >>> my problem in the first place!! I should have known better; all >>> I had to do was remove some of the outdated kernel files. And >>> when I did the dumb thing of deleting the /boot files, they were >>> moved into the "protected" .Trash-boot directory. >> >> OK, now let us know exactly what you have. Is it CentOS 4 as I expected? >> If so, the listing of files in /boot should look like so: >> >> [root@abc ~]# ls -laR /boot/ >> /boot/: >> total 3771 >> drwxr-xr-x 4 root root 1024 Mar 3 11:31 . >> drwxr-xr-x 24 root root 4096 Mar 3 11:37 .. >> -rw-r--r-- 1 root root 51676 Feb 18 07:41 config-2.6.9-100.EL >> drwxr-xr-x 2 root root 1024 Mar 3 11:31 grub >> -rw-r--r-- 1 root root 1364958 Mar 3 11:20 initrd-2.6.9-100.EL.img >> drwx------ 2 root root 12288 Jul 8 2005 lost+found >> -rw-r--r-- 1 root root 9371 Aug 13 2006 message >> -rw-r--r-- 1 root root 9371 Aug 13 2006 message.ja >> -rw-r--r-- 1 root root 67797 Feb 18 07:41 symvers-2.6.9-100.EL.gz >> -rw-r--r-- 1 root root 770652 Feb 18 07:41 System.map-2.6.9-100.EL >> -rw-r--r-- 1 root root 1538264 Feb 18 07:41 vmlinuz-2.6.9-100.EL >> >> /boot/grub: >> total 198 >> drwxr-xr-x 2 root root 1024 Mar 3 11:31 . >> drwxr-xr-x 4 root root 1024 Mar 3 11:31 .. >> -rw-r--r-- 1 root root 82 Aug 9 2005 device.map >> -rw-r--r-- 1 root root 7956 Aug 9 2005 e2fs_stage1_5 >> -rw-r--r-- 1 root root 7684 Aug 9 2005 fat_stage1_5 >> -rw-r--r-- 1 root root 6996 Aug 9 2005 ffs_stage1_5 >> -rw------- 1 root root 589 Mar 3 11:31 grub.conf >> -rw------- 1 root root 593 Aug 9 2005 grub.conf.orig >> -rw-r--r-- 1 root root 7028 Aug 9 2005 iso9660_stage1_5 >> -rw-r--r-- 1 root root 8448 Aug 9 2005 jfs_stage1_5 >> lrwxrwxrwx 1 root root 11 Aug 9 2005 menu.lst -> ./grub.conf >> -rw-r--r-- 1 root root 7188 Aug 9 2005 minix_stage1_5 >> -rw-r--r-- 1 root root 9396 Aug 9 2005 reiserfs_stage1_5 >> -rw-r--r-- 1 root root 3605 Aug 13 2006 splash.xpm.gz >> -rw-r--r-- 1 root root 512 Aug 9 2005 stage1 >> -rw-r--r-- 1 root root 103816 Aug 9 2005 stage2 >> -rw-r--r-- 1 root root 7272 Aug 9 2005 ufs2_stage1_5 >> -rw-r--r-- 1 root root 6612 Aug 9 2005 vstafs_stage1_5 >> -rw-r--r-- 1 root root 9308 Aug 9 2005 xfs_stage1_5 >> >> /boot/lost+found: >> total 14 >> drwx------ 2 root root 12288 Jul 8 2005 . >> drwxr-xr-x 4 root root 1024 Mar 3 11:31 .. >> >> 1) I don't know which tool you have used to move things to "Trash" but >> you >> should be aware that it may well be the case that some permissions and >> or >> file types like symlinks may not be correct after recovering from >> "Trash". >> >> 2) The directory "lost+found" can be recreated using the command >> 'mklost+found' >> >> 3) I'm not sure on how to make grub work again, but maybe some steps qre >> required after copying everything back to /boot. I hope someone else can >> give you better info about this. >> >> Simon >> >> > > > Wouldn't it have been easier to reinstall the kernel & grub, i.e.: > > yum reinstall kernel grub > > Surely if yum reinstalls it, it would re-create the permissions & > symlinks as well? Yes, only that reinstall doesn't exist in EL4 :) Simon

5 5

keepalived+LVS
by bedo 10 Mar '11

10 Mar '11

hello, all! if i want to use lvs function of keepalived , i must install ipvsadm ? tks!

4 9

Re: [CentOS] Server hangs on CentOS 5.5
by Michael Eager 10 Mar '11

10 Mar '11

Rudi Ahlers wrote: > As far as I can see you were giving a bucked load of advice, which you > haven't even bothered to follow yet. You're the only one who could > actually do anything about the problem. I have followed quite a bit of the advice, which I have appreciated and noted. I've set up the monitor so that it will not be blanked on a crash, installed monitoring software, and checked a number of conditions which people have suggested. No, I have not responded to the philosophical discussions about vender management, nor to the suggestions to RMA something to somebody for unknown reasons. No, I'm not going to replace RAM or capacitors here and there on the off chance that something might be bad. (But I will look for capacitors which show signs of bulging or leaking.) > No amount of suggestions made on this list will fix the problem for > you. You need to actually take apart the server and see what's going > on. I wasn't interested in anyone fixing the server for me. I did ask for suggestions on how improve the diagnostics for the problem, which several people have responded to. Again, I appreciate their suggestions greatly. As I've said, I have a list of things to check when the server is next taken down. -- Michael Eager eager(a)eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077

1 0

Re: [CentOS] Server hangs on CentOS 5.5
by Michael Eager 09 Mar '11

09 Mar '11

Rudi Ahlers wrote: > On Thu, Mar 10, 2011 at 12:31 AM, Michael Eager <eager(a)eagerm.com> wrote: >> Dr. Ed Morbius wrote: >> >>> If the issue is repeated but rare system failures on one of a set of >>> similarly configured hosts, I'd RMA the box and get a replacement. End >>> of story. >> I'll repeat: this is a house-made system. There's no vendor to RMA to. > > > > I don't know where you are, but in our country we can RMA anything and > everything. Apart from CPU's. So, even a cheap desktop mobo could be > RMA'd, as long as I can prove to the suppliers it's faulty, and it's > within the warrenty period I responded to Dr. Morbius' suggestion that I "RMA the box". There is vendor to RMA the box to. If I knew that it was a motherboard problem, I could RMA it. Or disk, or PSU, or network card, or whatever. But, as I've mentioned, there's no indication what causes the system to hang. There is no way at this point to prove that it is a defective motherboard. -- Michael Eager eager(a)eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077

2 1

[Newbie] Reclaiming /boot space
by Todd Cary 09 Mar '11

09 Mar '11

When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files. If I do a df -h, there is no available space yet it shows that it has a lot of used space. The fstab shows the following: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0 # fschk.ext3 /boot gives this error: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> I am not sure what I should do next. Thank you in advance for any suggestions... Todd -- Ariste Software Petaluma, CA 94952 http://www.aristesoftware.com

9 27

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