Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Getting rid of all the .rpmsave files
by Remco Barendse 14 Jan '06

14 Jan '06

Hi list! After yum upgrade of my CentOS 4.0 to 4.2 x86_64 box I now have countless .rpmsave files, about 90% of them I never touched or are config/start scripts. Does anyone have a neat script that will find all the rpmsave stuff in /etc and then prompts per file whether it can replace the original or not? Somehow doing this all by hand doesn't seem a very attractive idea :) Thanks!!

2 2

Why are dots in username & groupname no longer allowed?
by Remco Barendse 14 Jan '06

14 Jan '06

For some strange reason I am no longer able to create groupnames or usernames (with useradd and groupadd) that contain a dot. Uptill now it was possible to create user&groupnames like c.smith but now I get these errors: [root@server etc]# useradd c.smith useradd: invalid user name 'c.smith' [root@server1 etc]# groupadd c.smith groupadd: c.smith is a not a valid group name Anything without a dot works without problems. The box is a (fully updated) CentOS 3.6 x86_64 box with Dual Opteron cpu. Thanks for any hints!

10 12

RE: [CentOS] "find" statement: 64bit related??
by Bowie Bailey 14 Jan '06

14 Jan '06

rado wrote: > On Fri, 2006-01-13 at 13:02 -0500, Bowie Bailey wrote: > > rado wrote: > > > hi! > > > 3 machines all run this same test script. 2 -i386, 1 x-64bit > > > machine. > > > > > > this line: > > > > > > if find / -mount -type f -mtime -1 -print0 | xargs -0 clamscan -l > > > \ $CLAMDAILY $CLAMEXCLUDES -r --no-summary | cut -d: -f1 > > > > $CHANGEDLOG; \ then > > > > > > the $CHANGEDLOG file... on the 32 bit boxes...oh, probably 220 > > > files. On the 64bit box 177,999 files lol (Centos 64bit > > > w/everything installed)! > > > > > > it seems to me that the system is disregarding "-mtime -1" > > > > > > sure has me puzzled! I have rechecked all of my assigned variables > > > over and over in the cfg file and the syntax of the functions in > > > the functions file that make up the whole "team". I can find > > > nothing remarkable relating to the 64 box's cfg. > > > > > > any suggestions? > > > > It seems to work fine on my 64-bit machines. > > > > Try running this to see what is being selected: > > find / -mount -type f -mtime -1 -print0 | xargs -0 ls -ld > > > new_files.txt > > > > With the 'ls -ld', you will see the modification times as well, so > > you can tell if it is really selecting the wrong files. > > > yes, it really is selecting the wrong files...getting all kinds of > dates... Time for the mantra of computer techs around the world: "Hmm...that's odd...it shouldn't do that..." Don't know what else to tell you. Anyone else have any ideas? -- Bowie

4 5

ATI not supporting dpms
by Sam Drinkard 14 Jan '06

14 Jan '06

This workbox was thrown together with only a little bit of thought as to what the role would ultimately be, and at the time, I did not think it would ever wind up serving linux applications. Error #1 (my fault) Having a healthy pocketbook when I went into pick things up, I had already decided I wanted a good relatively mid-range graphics card, and I chose the ATI X600. (Error #2) As it turns out, the machine does absolutely nothing I ever intended for it to do, and probably will never fall into the role of a M$ server of any sort. Chalk one up for the good guys! To reduce the number of trips or exchanges back and forth to get it corrected (if that is possible) the software still does not work. Snowman

1 0

"nv" driver lock up where new version
by Jerry Geis 14 Jan '06

14 Jan '06

Jim, I have posted my xorg.conf file as you can see I have the 1920x1080 information. I post the log file saying nvidia is not accepting the line. The nv driver works at the 1920x1080 information it just doesnt seem stable. jerry ----------------- Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "LCD Panel 1920x1200" HorizSync 31.5 - 90.0 VertRefresh 60.0 - 60.0 ModeLine "1920x1080" 138.5 1920 1968 2000 2080 1080 1082 1087 1111 -hsync +vsync Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "Videocard vendor" BoardName "NVIDIA GeForce FX (generic)" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 16 Modes "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1080" "1600x1200" "1400x1050" "1280x1024" "1280x960" "1024x768" "800x600" "640x480" EndSubSection EndSection --------------------------- (II) NVIDIA(0): Frequency information for DFP-0: (II) NVIDIA(0): HorizSync : 30.000-80.000 kHz (II) NVIDIA(0): VertRefresh : 50.000-75.000 Hz (II) NVIDIA(0): (HorizSync from EDID) (II) NVIDIA(0): (VertRefresh from EDID) (II) NVIDIA(0): Adding EDID-provided mode "1920x1080" for DFP-0. (II) NVIDIA(0): Monitor0: Using hsync range of 30.00-80.00 kHz (II) NVIDIA(0): Monitor0: Using vrefresh range of 50.00-75.00 Hz (II) NVIDIA(0): Clock range: 12.00 to 135.00 MHz (II) NVIDIA(0): Not using mode "1920x1080" (bad mode clock/interlace/doublescan)

2 1

"nv" driver lock up where new version
by Jerry Geis 14 Jan '06

14 Jan '06

I have had my "nv" driver lock up a number of times. I downloaded the "nvidia" drivers and they did not work at 1920x1080 resolution. I am looking for an updated driver for just "nv". I found some once for a different driver that you just update commonXXX and yourdriverXXX not the whole X recompile. Where can I find those drivers? THanks, Jerry

2 1

snmp monitoring application
by Aniseko Ioane 14 Jan '06

14 Jan '06

what a better snmp app for centos?

3 3

Re: [CentOS] Printing Postscript - Very Weird Problem.
by C.M. Connelly 13 Jan '06

13 Jan '06

"MZ" == Maciej Żenczykowski <maze(a)cela.pl> MZ> Hey folks, okay, here's the situation - I have a Centos MZ> 4.2 system with cups printing installed printing via MZ> postcript (with appropriate PPD file) to a HP LaserJet MZ> 1320N printer (via jetdirect socket 9100). I have the same setup.... MZ> Everything seems to work right - except for an unusual MZ> 'font'??? problem. Many letters seem to be just slightly MZ> garbled. I have also seen this problem, generally when printing a PDF file (generated with TeX) from gv. If I open the file in Acrobat, it prints fine. I just tried generating some PostScript by piping the output of a command that produces ASCII through ``a2ps -1'', and I see no issues with the printout. If I take a simple LaTeX document and TeX it, producing a DVI file; then run dvips to produce a PostScript file and print that file From gv, I see no issues. On the other hand, if I run that same PostScript file through ps2pdf, then open the PDF file in gv and print it, I see the broken/malformed character issue. Running pdflatex on the source file to get a PDF file gives the same results: looks fine on screen, prints with broken/malformed characters from gv; prints fine from Acrobat. I had the very same problem with a LaserJet 1200 connected via a parallel cable under CentOS 3 a while back, and never really figured out what the deal was beyond this point. The obvious candidate is GhostScript, or gv's use of GhostScript to generate PostScript from the PDF file. Sorry I can't be more specific about what the cause is or a better solution, but at least you know you're not alone in having the problem! Claire P.S. On Will's question -- self tests work fine. It's definitely not the printer, unless it's some weird interaction between its emulated-PostScript interpreter and GhostScript. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

1 0

RE: [CentOS] "find" statement: 64bit related??
by Bowie Bailey 13 Jan '06

13 Jan '06

rado wrote: > hi! > 3 machines all run this same test script. 2 -i386, 1 x-64bit machine. > > this line: > > if find / -mount -type f -mtime -1 -print0 | xargs -0 clamscan -l \ > $CLAMDAILY $CLAMEXCLUDES -r --no-summary | cut -d: -f1 > $CHANGEDLOG; > \ then > > the $CHANGEDLOG file... on the 32 bit boxes...oh, probably 220 files. > On the 64bit box 177,999 files lol (Centos 64bit w/everything > installed)! > > it seems to me that the system is disregarding "-mtime -1" > > sure has me puzzled! I have rechecked all of my assigned variables > over and over in the cfg file and the syntax of the functions in the > functions file that make up the whole "team". I can find nothing > remarkable relating to the 64 box's cfg. > > any suggestions? It seems to work fine on my 64-bit machines. Try running this to see what is being selected: find / -mount -type f -mtime -1 -print0 | xargs -0 ls -ld > new_files.txt With the 'ls -ld', you will see the modification times as well, so you can tell if it is really selecting the wrong files. -- Bowie

2 1

system-config-users error
by Jeff Montagna 13 Jan '06

13 Jan '06

Has anyone seen this error before in CentOS 4.2? I've been setting up two identical systems, one has this error and the other doesn't. Short of removing and re-installing all the packages related to gtk is there an easier solution? I have removed and re-installed all the system-config tools, but the error didn't change. sudo system-config-users ** (system-config-users.py:27349): WARNING **: entry is incorrectly formatted (system-config-users.py:27349): GLib-GObject-CRITICAL **: file gvaluearray.c: line 42 (g_value_array_get_nth): assertion `value_array != NULL' failed ** ERROR **: file lib/user.c: line 662 (merge_ent_array_duplicates): should not be reached aborting... /usr/share/system-config-users/system-config-users: line 4: 27349 Aborted /usr/bin/python2 /usr/share/system-config-users/system-config-users.py Jeff Montagna

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss