Discuss

discuss@lists.centos.org

34753 discussions

Openssh and CentOS
by Denis Machard 08 Nov '06

08 Nov '06

I would like to know why the version of openssh used in Centos4.4 is based on version 3.9p1 but not on a more recent version of openssh? The vulnerabilities found and corrected in the last version of openssh are also corrected in version 3.9?

3 3

RE: [CentOS] Mirroring CentOS problem.
by Mark Schoonover 08 Nov '06

08 Nov '06

S.C.A. S.r.l. wrote: > I have two servers that, one time in a week, make a mirror o CentOS > distribution, the mirroring come from two different italian servers > but all the mirrors process stops with this message: > > sent 267 bytes received 374865 bytes 44133.18 bytes/sec > total size is 6472762072 speedup is 17254.63 > rsync error: some files could not be transferred (code 23) at > main.c(1146) > > What's the problem? > Ps excuse me for my english. > > Regards > Amedeo Fragai > S.C.A. S.r.l. Amedeo, Don't worry about your English, it's way better than my Italian! :) There are several reasons to get a code 23 error with rsync. One of them being disappearing files. You might have temp files that get into the rsync filelist before rsync transfers files. Once rsync starts transferring the files, and if any of those files are now gone from the filesystem, rsync will generate the code 23 error. Do you log the output from rsync?? That could give you more information as to the exact problem. HTH Thanks! Mark Schoonover IS Manager American Geotechnical V: 858-450-4040 - F: 714-685-3909 - C: 858-472-3816 "Stop the Earth!! I want off!!"

3 2

Problem rkhunter v. 1.2.8 - CENTOS 4
by Adriano Frare 08 Nov '06

08 Nov '06

Dear Friends, I am using CENTOS 4.3 - kernel 2.6.9-42.0.2.EL with rkhunter version 1.2.8, but the rkhunter program show me problem on file /bin/kill. I compare files /bin/kill with other CENTOS 4 and it has same size. ====================== SHOE LOG =========================== Rootkit Hunter 1.2.8 is running Mon, 30 Oct 2006 12:56:44 -0200 Determining OS... Ready Checking binaries * Selftests Strings (command) [ OK ] * System tools Info: prelinked files found Performing 'known good' check... /bin/cat [ OK ] /bin/chmod [ OK ] /bin/chown [ OK ] /bin/date [ OK ] /bin/dmesg [ OK ] /bin/env [ OK ] /bin/grep [ OK ] /bin/kill [ BAD ] /bin/login [ OK ] /bin/ls [ OK ] /bin/more [ OK ] /bin/mount [ OK ] /bin/netstat [ OK ] /bin/ps [ OK ] /bin/su [ OK ] =========================================================== I guess problem is rkhunter. Thanks for help. Adriano Frare

4 5

Update icon cache
by Michael Velez 07 Nov '06

07 Nov '06

Hello all, How can I update the icon cache in /usr/share/icons/gnome? I tried gtk-update-icon-cache but the command is not found. Thanks, Michael

2 5

RE: [CentOS] Desktop cleared after reboot through VNC
by Craig White 07 Nov '06

07 Nov '06

On Tue, 2006-11-07 at 13:58 -0500, Michael Velez wrote: > > On Tuesday 07 November 2006 03:18, Michael Velez wrote: > > > I guess I corrupted the desktop when I rebooted through VNC > > but I don't know > > > how to get it back. > > > > > > Is there a way of retrieving this without having to delete > > this user and > > > creating a new one? > > > > Guessing sucks. Always try to figure out what's going on! > > Leaving this unknown > > can only lead to trouble down the road - it's always better > > to spend some > > time and find out whassup. You'll find out something bad has > > happened, or > > you'll learn how to better identify if something bad is > > happening later. > > Either way, you're ahead! > > > > Different WM have different locations for Desktop. KDE's > > desktop is usually in > > ~/Desktop. Check out that folder. > > > > If you really think corruption is in order, you might want to > > check your > > entire f/s with e2fsck: > > > > # shutdown -Fr now; > > > > Otherwise, you might have to recover from backups. (you DO > > have backups, > > right?) > > > > Actually, when I meant I corrupted the desktop, I didn't mean at a disk > level. I doubt e2fsck will fix this (although I'll run it anyway, you never > know). The reboot was proper; however, it was done through VNC which seems > to have caused a different chain of events when closing the gnome-session. > This is what I'm trying to figure out. > > As I mentioned in my previous e-mail all my *.desktop files are in my > ~/Desktop directory. They just do not appear on the desktop when I open my > gnome session. The session starts everything else (start menus, taskbar, > startup applications - i.e. xclock) it's just my desktop that has become one > solid color (dark blue) with no icons. I can log in fine with other > userid's and receive a good desktop, so this really has something to do with > my user profile. > > At this point, I'm trying to figure out how a reboot through VNC could have > made my gnome-session close improperly. > > I don't know enough about gnome-sessions to figure this out myself. Is > there a file in the gnome profile that has desktop information (other than > ~/Desktop)? > > I've had to use VNC a lot lately so I have seen this once before. I > couldn't figure it out and I just deleted the user, created a new one, and > re-installed user files from backup (which I have a wazoo of; I have more > automated backup than a home environment actually needs). My next e2fsck > after that did not mention a corruption so it really has to be something in > my profile files. ---- ~/Desktop is the objects on your desktop (files / folders / etc.) your settings are typically stored in ~/.gnome or ~/.gnome2 or ~/.gconf try moving them... mv .gnome .gnome-bak one at a time and then log in again and see what works. Moving them rather than deleting them allows you to recover settings that you might want to keep Craig

2 1

gnbd vs drbd
by Rodrigo Barbosa 07 Nov '06

07 Nov '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Up until now, I have been using drbd for file custers with great success. Yes, it is a PITA, and sometimes you can get annoying sincronization issues (mostly on lab situations). Now I have been considering giving gnbd (with cs/gfs) a try. Do any of you ever crossed this path ? Any comparisons or comments ? TIA, - -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFT/Z1pdyWzQ5b5ckRAiXlAJ9gAJNtx7amdZJ2gKfAsxmRSCm/zwCfYy9D zr7kN3JjBz1HY/5zgT0ylq8= =6FOA -----END PGP SIGNATURE-----

4 6

Desktop cleared after reboot through VNC
by Michael Velez 07 Nov '06

07 Nov '06

Hello all, After issuing the reboot command on my CentOS server while being logged in through VNC and after the machine has actually rebooted, I get a blank desktop (no icons and not my default wall paper) when logging into X, whether I'm on the console or logging in through VNC. If I go into my Desktop folder in my home directory, I see all the appropriate .desktop files (but I don't see the icons on my actual desktop). When I go to the Preferences->Desktop menu, the desktop preferences application hangs. My toolbars, and default xclock at startup are all there, it's just that my desktop is a solid blue wallpaper (not my default CentOS wallpaper) and I have no icons on it. I guess I corrupted the desktop when I rebooted through VNC but I don't know how to get it back. Is there a way of retrieving this without having to delete this user and creating a new one? Thanks, Michael

2 2

CentOS-announce Digest, Vol 21, Issue 3
by centos-announce-request＠centos.org 07 Nov '06

07 Nov '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:0730 Important CentOS 3 i386 php - security update (Tru Huynh) 2. CESA-2006:0730 Important CentOS 3 x86_64 php - security update (Tru Huynh) 3. CESA-2006:0730 Important CentOS 3 s390(x) php - security update (Pasi Pirhonen) 4. CESA-2006:0730 Important CentOS 4 s390(x) php - security update (Pasi Pirhonen) 5. CESA-2006:0730 Important CentOS 3 ia64 php - security update (Pasi Pirhonen) 6. CESA-2006:0730 Important CentOS 4 ia64 php - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Tue, 7 Nov 2006 11:23:30 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2006:0730 Important CentOS 3 i386 php - security update To: centos-announce(a)centos.org Message-ID: <20061107102330.GA16571(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2006:0730 php security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2006-0730.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/php-4.3.2-37.ent.i386.rpm updates/i386/RPMS/php-devel-4.3.2-37.ent.i386.rpm updates/i386/RPMS/php-imap-4.3.2-37.ent.i386.rpm updates/i386/RPMS/php-ldap-4.3.2-37.ent.i386.rpm updates/i386/RPMS/php-mysql-4.3.2-37.ent.i386.rpm updates/i386/RPMS/php-odbc-4.3.2-37.ent.i386.rpm updates/i386/RPMS/php-pgsql-4.3.2-37.ent.i386.rpm source: updates/SRPMS/php-4.3.2-37.ent.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update php\* Tr -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Segmentation fault on LVM
by C. L. Martinez 07 Nov '06

07 Nov '06

Hi all, I have installed rhcs on a CentOS 4.4 server with clvmd. When server reboots display a segmentation fault on line 504 in /etc/rc.d/rc.sysinit file, here: if [ -x /sbin/lvm.static ]; then 500 if /sbin/lvm.static vgscan --mknodes --ignorelockingfailure > /dev/null 2>&1 ; then 501 action $"Setting up Logical Volume Management:" /sbin/lvm.static vgchange -a y --ignorelockingfailure 502 fi 503 fi 504 fi I don't use lvm on root filesystem, only on a gfs volumes: [root@keops RPMS]# df -h Filesystem Size Used Avail Use% Mounted on /dev/hda1 5.8G 791M 4.7G 15% / none 379M 0 379M 0% /dev/shm /dev/mapper/gfsvol01-cludatavol01 64G 357M 63G 1% /gfsdata Why?? On a RHEL 4 U4 AS, this error doesn't occur .... My lvm packages are: [root@keops RPMS]# rpm -qa |grep lvm |sort lvm2-2.02.06-6.0.RHEL4 lvm2-cluster-2.02.06-7.0.RHEL4 Can somebody help me?? Many thanks.

2 2

Fwd: Warning: Kernel/Config.pm isn't writable! -- OTRS error -CENTOS 4.4
by Indunil Jayasooriya 07 Nov '06

07 Nov '06

Hi, I am trying to install OTRS on centos 4.4. I keep getting Warning: Kernel/Config.pm isn't writable! when i try to run the installer. I have done chmod 777 on the Config.pm file etc but still it will not work. I also did "chown Config.pm apache" and that did not work either. Please can someone help me. This looks like a simple issue which i cannot able to solve. below is the error. Warning: Kernel/Config.pm isn't writable! *Comment:* If you want to use the installer, set the Kernel/Config.pm writable for the werserver user! -- Thank you Indunil Jayasooriya -- Thank you Indunil Jayasooriya

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