Discuss

discuss@lists.centos.org

34753 discussions

printing problem
by umair shakil 14 Nov '07

14 Nov '07

Salam, I am using CentOs 4.4, i have network printer with ip 192.168.1.88. when i click the option to print document, it seems everything is OK, printer shows with bliking of Data light but no print..... what i am missing??? Regards, Umair Shakil ETD

4 5

freenx
by Michael Oevermann 14 Nov '07

14 Nov '07

Hello, I am having problems getting freenx running in CentOS 4.5 i386_64. I know this is not a new problem, however, I havn't found a solution in all the postings I found on the web. I did exactly what is supposed to work and described in detail at http://wiki.centos.org/HowTos/FreeNX After doing that I can connect to the server with nxcleint without problem but I get only a black screen. In the files .nx/S.../session and errors I see the warning Warning: Unrecognized session type 'unix-gnome'. Assuming agent session. The same happens with KDE. With the command nxloadconfig --check I get the output Warning: Could not find nxdesktop in /usr/bin. RDP sessions won't work. Warning: Could not find nxviewer in /usr/bin. VNC sessions won't work. Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=/usr/lib/ libX11.so.6.2:/usr/lib/libXext.so.6.4:/usr/lib/libXcomp.so.2:/usr/lib/ libXcompext.so:/usr/lib/libXrender.so.1.2". /usr/lib/libX11.so.6.2 could not be found. Users will not be able to run a single application in non-rootless mode. Warning: Invalid value "COMMAND_FOOMATIC=/usr/lib/cups/driver/ foomatic-ppdfile" Users will not be able to use foomatic. Warning: "/usr/lib/cups/backend/nxipp" is not executable. Users will not be able to enable printing. Warning: "/usr/lib/cups/backend/smb" is not executable. Users will not be able to enable printing. Warning: Invalid value "COMMAND_START_CDE=cdwm" Users will not be able to request a CDE session. Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2. Users will not be able to enable printing. Error: Could not find 1.5.0 or 2.[01].0 or 3.0.0 version string in nxagent. NX 1.5.0 or 2.[01].0 or 3.0.0 backend is needed for this version of FreeNX. Errors occured during config check. Please correct the configuration file. The libraries are definitely not where nx looks for them - they are located at /usr/lib64/NX/lib (and symlinks under (usr/lib/NX/lib). What is going wrong here? I also tried to use nxconfig with --setup- nomachine-key with the same results, except that I did not need to import the key in the nxclient anymore. Does anyone has an idea to solve the problem? Many thanks for help Michael

3 3

configuring sendmails domain
by Jerry Geis 14 Nov '07

14 Nov '07

I tried editing sendmail.cf and changing the Dj line to X.com so any email originating from my machine would be X.com not m.X.com where m is machine name. I typed make in the /etc/mail directory and did service sendmail restart. This did not work. email still shows as m.X.com What am I missing so as to NOT have the machine name in the email address. I just want the domain. Thanks, Jerry

4 5

Sso the Linux way?
by Jason Pyeron 14 Nov '07

14 Nov '07

So I was googling around about this over the last week and here is what I found: nis/yp is for some reason bad. Kerbos is holy, but no how-to's that don't involve windows and active directory. What is the recommended sso approach for centos? Where are there examples / docs to follow? Jason -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Sr. Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited.

5 4

Centos5 install failure
by John Thompson 14 Nov '07

14 Nov '07

A couple weeks ago I attempted to install Centos5 to replace an increasingly decripit Fedora Core 1 installation. Centos went onto an 80GB piece of previously unallocated space on /dev/hda, using the default configuration offered by anaconda. The installation process went smoothly, however, I was unable to boot Centos when it completed due to "Grub failure." IOW, I never even got the boot loader to come up. I've never been a big fan of grub (I've always used lilo) and this hasn't impressed me. I was able to restore Fedora's lilo loader but I cannot persuade lilo to boot Centos, probably because the / filesystem is using LVM which I am not familiar with. It failed with a kernel panic trying to find things in /dev. I put it on the back shelf for a couple weeks and finally got back to it today. I wiped hda to give it a fresh base on which to install, and it installed fine once again -- no errors. But on reboot grub failed once again, getting as far as GRUB and then locking up, responding only to the RESET button. So I created a bootable grub CD and booted from that, fed it the Centos kernel and initrd and booted. Lots of "missing module" errors because (as it turns out) the Centos installer neglected to create the proper module tree in /lib/modules. But there was one for the xen kernel. WTF, I'll try that. Boot again and tried to tell grub to load the xen kernel: "invalid file format." Whatever. Booted the regular kernel and initrd again, gritting my teeth through all the errors and created a sym-link from the xen module tree to what should be the regular module tree. Rebooted again with the regular kernel and initrd. Fewer error messages this time, but still a fair number. I just wanted to get to the point were I could repair the missing modules. So the system comes up -- sort of. The modules that still couldn't load turned out to include those for my network card, so no network access. Nor could I mount any cds or the xfs file system on the raid array. Useless. Just frickin' useless. My low opinion of grub remains unchanged, and my opinion of Centos is following in the same direction. I spent the rest of the afternoon restoring Fedora off my backup tapes. Any clues what I did wrong? -- John (john(a)os2.dhs.org)

6 14

Retrieving a banned e-mail
by Rajeev R Veedu 14 Nov '07

14 Nov '07

We have a postfix+cyrus+Spamassassin setup and all the virus or Banned or spam e-mails will move to a folder on /var/virusmails. I have a falseposative mail moved due to a banned attachment name. Could you please help me to retrieve these e-mails? Thanks Rajeev R. Veedu

3 5

Web DAV (folder) access fails
by Kenneth Porter 13 Nov '07

13 Nov '07

I'm trying to get web folder (DAV) access working to my CentOS 5 setup. I previously had it working fine under Fedora 2. I can access the folder with the Java-based DAVExplorer, but Windows Network Places won't let me "Add a Network Place", telling me that "The folder you entered does not appear to be valid". I'm using https with self-signed cert and htpasswd file. If I switch to non-SSL, Windows recognizes the URL as valid, but my logins all fail with a 401. I don't see any clues in the Apache logs, and I'm not sure where to look next.

1 2

New machine dying on boot.... - CPU 0 not enough memory for domain -
by John Plemons 13 Nov '07

13 Nov '07

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

3 8

Persistent iSCSI Device Names on CentOS 4
by Jay Leafey 13 Nov '07

13 Nov '07

I found a lot of stuff about this on the web, but never an answer that worked. One of the most promising hints was about udev maintaining links in the /dev/disk/by-* directories. This works just fine in CentOS 5, but not CentOS 4. As I was trying to use the iSCSI devices as VMware disks this was particularly frustrating. After banging my head on this for a while, I figured out how to make it work. By default, iSCSI devices don't show up in the /dev/disk/by-* directories maintained by udev under CentOS 4. After looking at the scripts used by udev, it appeared that the scsi_id program was not returning anything for the iSCSI devices. Digging in the manpage and the /etc/scsi_id.config file led me to believe that the devices in question were "blacklisted" and never returned a valid device ID. The fix was to add a line to scsi_id.config to whitelist the particular devices. In my case, the iSCSI devices are provided by on Openfiler box, which shows up in /proc/scsi/scsi like this: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: Openfile Model: Virtual disk Rev: 0 Type: Direct-Access ANSI SCSI revision: 04 The fix for me was to add the following line to my iscsi_id.config file: vendor=Openfile, model="Virtual disk", options=-g The values for "vendor=" and "model=" will vary with the specific iSCSI target used. After adding this and rebooting, udev now properly maintains the links in /dev/disk/by-id/ for each of the iSCSI devices offered up to my workstation. Hope that helps somebody! -- Jay Leafey - Memphis, TN jay.leafey(a)mindless.com

1 0

Best laptop for CentOS
by Ern jura 13 Nov '07

13 Nov '07

Which is the best laptop to run centos on and where can I buy one without Windows Vista pre loaded cause I will uninstall it any way. Please tell me the best sites that ship worldwide.

12 12

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