Discuss

discuss@lists.centos.org

34758 discussions

Start a nNew thread

Re: [CentOS] CentOS post acknowledgement
by Darr247 12 Jan '12

12 Jan '12

Hmmmm... well THAT doesn't seem right - getting 2 post acknowledgements to a single message.

1 0

Re: [CentOS] USB install annoyances
by Darr247 12 Jan '12

12 Jan '12

On Tuesday, January 10, 2012 17:53 [UTC -5], Darr247 spake thusly: > I did not see that synopsis in your original post (and I'm not sure I > could figure out what commands you used by that). > The only 2 replies to this thread I saw in digest 84 issue 9 were to > John Doe. > > Anyway, this is what I have in my notes, though I see you've marked > this as solved... > > mostly assuming sdb as the USB device. > > From blank USB stick to bootable install: > > yum install livecd-tools syslinux > dd if=/dev/zero of=/dev/sdb bs=512 count=1000 > parted /dev/sdb mklabel msdos > parted /dev/sdb mkpartfs p ext2 0% 100% > tune2fs -m0 /dev/sdb1 Oh, and sometimes the tune2fs command isn't needed. If I recall, it's needed only if the stick has never been formatted. > parted /dev/sdb toggle 1 boot > umount /dev/sdb1 > livecd-iso-to-disk <path to>/DVD.iso /dev/sdb1 > > mkdir /mnt/iso > mount -o loop <path to>/DVD.iso /mnt/iso > mkdir media<usb stick>/images > cp /mnt/iso/images/install.img media<usb stick>images > cp <path to>/DVD.iso /media/<usb stick>/ > > TEST: > qemu -m 512 /dev/sdb > > > I guess I should add > yum install qemu > to my notes, as I don't think that's installed by default. > > But using livecd-iso-to-disk makes it NOT ask for the image file > location during the install. Try it. > > Personally, I think they should've named it bootable-iso-tools, but > everyone's probably used to the livecd-tools name by now.

1 0

Re: [CentOS] USB install annoyances
by Darr247 12 Jan '12

12 Jan '12

1 0

CPU Usage when idle
by Jorge Fábregas 12 Jan '12

12 Jan '12

Hello guys, Did anyone noticed how green CentOS 6 is compared to the previous release? I've been running a couple of "CentOS 6" VMs (on our vSphere environment) for the last couple of weeks and noticed a BIG difference when it comes to CPU usage when the VM is completely idle. I would like to share what I've seen in our environment: PfSense 2.0 (FreeBSD) VM: 40 Mhz CentOS 5.7 VM: 60 Mhz CentOS 6.2 VM: 5 Mhz This is really wonderful. They did a great job with RHEL6 and I'm curious what was changed in order to accomplish this. Regards, Jorge

2 1

Building REDHAT Desktop Virtualization Solution With Centos
by Arif Tuhin 12 Jan '12

12 Jan '12

Redhat offers a desktop virtualization solution using "kvm,qemu,libvirt and spice" which is directed at centralized server hosting virtual desktops and thin clients connecting to it. All the relevant software are open source. So it should be possible to achieve the same feat with CentOS. Anyone know any complete tutorial regarding this? I've found separate tutorials regarding spice, kvm etc. But a complete tutorial describing how to emulate the "Redhat virtualization for Desktops" will be very handy. Thanks in advance.

3 2

Centos 5.7, I10 video, 1920x1080 monitor
by Frank Cox 12 Jan '12

12 Jan '12

I have a Centos 5.7 machine with Intel I10 video (built-in, I guess -- this is one of those all-in-one mini terminal things) that I'm trying to put a new 1920x1080 monitor onto, without conspicuous success. Prior to this it's been using a smaller monitor with no issues. Try as I might I can't get the new monitor to run at its 1920x1080 resolution. I just realized that I forgot to write down the actual resolution that it runs at but it's less than it should be, maybe 1280x1024? Obviously the display looks pretty crappy like that. I tried following the instructions posted here: http://www.ubuntugeek.com/how-change-display-resolution-settings-using-xran… but when I got to the step of typing "xrandr --newmode ..." all I got was a help screen for xrandr command line options (and --newmode wasn't listed as one of them). I tried this: system-config-display --reconfig --set-resolution=1920x1080 --set-depth=24 --set-driver=vesa --set-videoram=0 It rewrote the xorg.conf file but I still didn't get 1920x1080. I tried changing "vesa" to "i810" in xorg.conf and was then told that the xserver can't be started. It then took me to a simple GUI-style monitor setup screen and I told it that a 1920x1080 LCD monitor was connected. It then created the following xorg.conf, but I still don't get 1920x1080. The Xorg.0.log file is over 2000 lines so I won't include it in this mesage but I have posted it here: http://www.melvilletheatre.com/Xorg.0.log.bz2 Here is what I currently have for xorg.conf but again, it doesn't give me the full resolution on the monitor: # Xorg configuration created by system-config-display Section "ServerLayout" Identifier "single head configuration" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "Monitor" Identifier "Monitor0" ModelName "LCD Panel 1920x1080" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 31.5 - 67.0 VertRefresh 56.0 - 65.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "vesa" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!

2 3

Re: [CentOS] Write to USB pendrives horribly slow
by m.roth＠5-cent.us 11 Jan '12

11 Jan '12

Blah, blah, blah, Being blocked again, still appears to be based on new content vs. included content. Which makes it very annoying when I want to include context for my response. blah, blah, blah, new content................. Hi, wwp, wwp wrote: > On Wed, 11 Jan 2012 16:31:43 +0100 Ljubomir Ljubojevic <office(a)plnet.rs> wrote: >> On 01/11/2012 08:45 AM, wwp wrote: >> > On Tue, 10 Jan 2012 08:57:14 -0800 (PST) John Doe<jdmls(a)yahoo.com> >> wrote: >> >> From: wwp<subscript(a)free.fr> >> >> >> >>> I wonder if some mount options aren't wrong with USB pendrives, see: >> >>> /dev/sdd1 on /media/monolith type vfat >> >>> (rw,nosuid,nodev,uhelper=udisks,shortname=mixed,dmask=0077,utf8=1,flush) my suspicion is about the flush option, which I find atypical here. <snip> > ehci_hcd does manage my devices (it's not a loadable module, apparently compiled in kernel instead), see for instance: > > kernel: usb 2-2: new high speed USB device using ehci_hcd and address 28 <snip> This may be a dumb question, but have you done an lsusb? I'd be curious - I know that on my brand new, as of a few months ago, Dell I have two kinds of USB ports, 1.1 and 2.0. We also have some 1.1 webcams... and some 1.0. See if your pen drive's in a slower port. mark

2 1

Clustering solutions - mail, www, storage.
by Rafał Radecki 11 Jan '12

11 Jan '12

Hi all. I am currently working for a hosting provider in a 100+ linux hosts' environment. We have www, mail HA solutions, as storage we mainly use NFS at the moment. We are also using DRBD, Heartbeat, Corosync. I am now gathering info to make a cluster with: - two virtualization nodes (active master and passive slave); - two storage nodes (for vm files) used by mentioned virtualization nodes (also active/passive). For virtualization I am thinking to use OpenVZ or KVM. For storage NFS or iSCSI. Could you please share your experiences with these technologies? Which one would you use and why? Are there any good alternatives in CentOS? Thanks for the info, Rafal.

4 3

EPEL not working ... is it just me?
by Alan McKay 11 Jan '12

11 Jan '12

This is very strange - has been happening the last few days. I just upgraded this system from 5.3 to 5.7 on Monday and the problem started some time after that (but not immediately because I know I used yum Monday evening after the upgrade) I get the following error from yum, but it goes away if I --disablerepo=epel The funny thing is that the listed xml file I can easily wget from this system. Also having the issue with other 5.7 systems that were upgraded from 5.3 several weeks ago and had been working fine since. I did some googling and found some things to try like "yum clean all" and I even deleted the rpm database based on advice from one site, and then rebuilt it from scratch. But nothing. [root@solexa-db varlog]# yum -y install hddtemp Loaded plugins: downloadonly, rhnplugin, security http://fedora.mirror.nexicom.net/epel/5/x86_64/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')> Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"

2 3

SELinux blocking cgi script from "writing to socket (httpd_t)"
by Bennett Haselton 11 Jan '12

11 Jan '12

Is this really supposed to get easier over time? :) Now my audit.log file shows that SELinux is blocking my cgi script, index.cgi (which is what's actually served when the user visits the front page of one of our proxy sites like sugarsurfer.com) from having '"read write" to socket (httpd_t)'. I have no idea what that means, except that I thought that cgi scripts were supposed to be able to write to stdout so that the web server could send the data via a socket connection to the end user's browser, so I don't know why a CGI script would be blocked from writing to a socket with security context httpd_t. The only clue that might narrow it down is the line "Target Objects socket [ udp_socket ]". The sockets that the cgi scripts usually send output to are of course tcp sockets, so why would it say udp? The only time one of my cgi scripts might use udp would be if it were doing a hostname lookup via dns, but the index.cgi script doesn't do that at any point. What would the pros do at this point? *** Summary: SELinux is preventing index.cgi (httpd_sys_script_t) "read write" to socket (httpd_t). Detailed Description: [SELinux is in permissive mode, the operation would have been denied but was permitted due to permissive mode.] SELinux denied access requested by index.cgi. It is not expected that this access is required by index.cgi and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Or you can disable SELinux protection altogether. Disabling SELinux protection is not recommended. Please file a bug report (http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against this package. Additional Information: Source Context system_u:system_r:httpd_sys_script_t Target Context system_u:system_r:httpd_t Target Objects socket [ udp_socket ] Source index.cgi Source Path <Unknown> Port <Unknown> Host <Unknown> Source RPM Packages Target RPM Packages Policy RPM selinux-policy-2.4.6-316.el5 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Permissive Plugin Name catchall Host Name g6950-21025.securedservers.com Platform Linux g6950-21025.securedservers.com 2.6.18-274.12.1.el5 #1 SMP Tue Nov 29 13:37:46 EST 2011 x86_64 x86_64 Alert Count 1 First Seen Wed Jan 11 09:34:13 2012 Last Seen Wed Jan 11 09:34:13 2012 Local ID 2adcd43d-7b8b-4e17-bb93-ad11a35f378a Line Numbers 1 Raw Audit Messages type=AVC msg=audit(1326303253.473:3626): avc: denied { read write } for pid=6668 comm="index.cgi" path="socket:[415055]" dev=sockfs ino=415055 scontext=system_u:system_r:httpd_sys_script_t:s0 tcontext=system_u:system_r:httpd_t:s0 tclass=udp_socket

3 4

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