Discuss

discuss@lists.centos.org

34758 discussions

Squid and SELinux
by Marcos Lois Bermúdez 02 Feb '11

02 Feb '11

Hi. I'm trying to setup squid with SELinux, the problem i encounter is taht i want to add another directory for cache, in this system we have a home partition with huge space, i create a squid dir and add the path with semanage: semanage fcontext -a -t squid_cache_t '/home/squid(/.*)?' i check the files and are in the good context: drwxr-xr-x squid squid user_u:object_r:squid_cache_t . drwxr-xr-x squid squid system_u:object_r:home_root_t .. drwxr-x--- squid squid user_u:object_r:squid_cache_t 00 drwxr-x--- squid squid user_u:object_r:squid_cache_t 01 ... But when i want start it i get this: type=AVC msg=audit(1296442326.932:739661): avc: denied { search } for pid=30924 comm="squid" name="/" dev=sda3 ino=2 scontext=user_u:system_r:squid_t:s0 tcontext=system_u:object_r:home_root_t:s0 tclass=dir I know that the solution is to mount the huge partition on /var/spool/squid, i'm a newbie to SELinux, and want to know if it's posible to archive this. Regards.

3 4

glibc++6.2?
by Hal Davison 02 Feb '11

02 Feb '11

Greetings ALL... V 5.5 Gnome. Desktop Looking for glibc++6.2 and higher. --Hal -- Hal Davison Observe Goal, Set the course, Burn the map Davison Consulting This correspondence was composed using Dragon Speaking Version 10 Peg#: 2007011701

7 8

Re: [CentOS] CentOS 6.0 new virtualization features?
by Matt 02 Feb '11

02 Feb '11

>> I am excited about CentOS 6.x though. Aren't there supposed to be >> some neat new features etc for virtualization and cloud computing? > > this could be the start of a dangerously long thread nonrelated to OP. > Why not start a new thread with 'CentOS-6 interesting upcoming features' :) Your right.

5 4

Re: [CentOS] RHEL-6 vs. CentOS-5.5 (was: Static assignment of, SCSI device names?)
by Chuck Munro 02 Feb '11

02 Feb '11

Les Mikesell wrote: > > On 1/30/11 1:37 PM, Chuck Munro wrote: >> > Hello list members, >> > >> > My adventure into udev rules has taken an interesting turn. I did >> > discover a stupid error in the way I was attempting to assign static >> > disk device names on CentOS-5.5, so that's out of the way. >> > >> > But in the process of exploring, I installed a trial copy of RHEL-6 on >> > the new machine to see if anything had changed (since I intend this box >> > to run CentOS-6 anyway). >> > >> > Lots of differences, and it's obvious that RedHat does things a bit >> > differently here and there. My focus has been on figuring out how best >> > to solve my udev challenge, and I found that tools like 'scsi_id' and >> > udev admin/test commands have changed. The udev rules themselves seem >> > to be the same. > Do any of the names under /dev/disk/* work for your static identifiers? You > should be able to use them directly instead of using udev to map them to > something else, making it more obvious what you are doing. And are these names > the same under RHEL6? > I was happy to see that device names (at least for SCSI disks) have not changed. The more I look into the whole problem the more I realize that I've overstated the difficulty, now that I know how to map out the hardware path for any given /dev/sdX I might need to replace. I've never dug as deeply into this before, mostly because I never could find the spare time. I'm happy with simply writing a little script which accepts a /dev/sdX device name argument and reformats the output of: 'udevadm info --query=path --name=/dev/sdX' to extract the hardware path. It's a bit cleaner than the current RHEL-5/CentOS-5 'udevinfo' command. Using the numeric path assumes knowledge of how the motherboard sockets are laid out and the order in which I/O controller channels are discovered, of course. It's then not difficult to trace a failed drive by attaching little tags to the SATA cables from the controller cards. The real key is to carefully label each SATA cable and its associated drive. Then the little mapping script can be used to identify the faulty drive which mdadm reports by its device name. It just occurred to me that whenever mdadm sends an email report, it can also run a script which groks out the path info and puts it in the email message. Problem solved :-) So even though I figured out how to add 'alias' symlink names to each disk drive, I'm not going to bother with it. It was a very useful learning experience, though. Chuck

2 1

Setting up persistent LUNs
by Dvorkin, Asya 02 Feb '11

02 Feb '11

Hello everyone, I am trying to setup persistent LUNs and having problems. I've been following instructions I found on the web and they refer to editing /etc/scsi_id.config file and adding options=-g line there. After doing so, I should be able to run scsi_id -g -s /dev/sd* and get proper results. I've modified file /etc/scsi_id.config appropriately: [root@psrwjmsafs1 etc]# grep options /etc/scsi_id.config vendor="ATA",options=-p 0x80 options=-g but whenever I run scsi_id -g -s /b/sde1 - i get nothing. [root@psrwjmsafs1 etc]# df -k |grep sde /dev/sde1 1754602560 93383616 1572090328 6% /test How come? Am i missing something? Thank you! Asya

2 2

limiting yum url question
by Xinhuan Zheng 02 Feb '11

02 Feb '11

Hi, I need to configure yum to limit the number of URLs going out for security reason. I don't find a configuration for include option. I do find an exclude option in /etc/yum/pluginconf.d/fastestmirror.conf. It would be impossible to exclude every url in this file. What is the best way to limit the traffic going out interest for yum? Is the local network repository a better way or does there exist an include option that I am not aware of? Thanks, --xinhuan

2 3

Re: [CentOS] what pkg contains libstdc++-libc6.2-2.so.3
by Les Bell 02 Feb '11

02 Feb '11

Hal Davison <hal(a)faams.net> asked as above: And the answer is: compat-libstdc++-296-2.96-138 (on Centos 5.5, that is). Best, --- Les Bell [http://www.lesbell.com.au] Tel: +61 2 9451 1144

1 0

CentOS 5 updates
by Ben McGinnes 02 Feb '11

02 Feb '11

3 6

Re: [CentOS] Kernel Errors Present...
by Keith Roberts 01 Feb '11

01 Feb '11

On Wed, 12 Jan 2011, John R Pierce wrote: > > To: centos(a)centos.org > From: John R Pierce <pierce(a)hogranch.com> > Subject: Re: [CentOS] Kernel Errors Present... > > >> In the BIOS I turn DMA off for /dev/hda and /dev/hdc, >> but they still show up in /proc/ide/.../settings as >> using_dma 1. > > > say HUH? IDE PIO modes are like 3-7 MBytes/sec and require 100% CPU > utilization during the transfer phase. why in dogs name would you be > doing this in 2011 ? ...snip... > January 12, 2011 06:26PM > Use the modern, 80 wire cables, and trust the technology - > it's come a long way. Thanks for all the replies concerning this. I have bought an off-the-shelf 24" round ATA 133 IDE cable, and installed that in place of the 40-wire cable. The problem now appears to be fixed. Been keeping an eye on my logwatch emails, and they are no longer reporting this problem. Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

1 0

How to relocate $HOME directory
by Soo-Hyun Choi 01 Feb '11

01 Feb '11

Hi there, As you know, $HOME is generally located at "/home/$username" by default. I would like to re-locate all users' $HOME directories to something like "/export/home/$username" without having a hassle/trouble. Initially, I've thought of just copying them to the new directory (under /export/home/xxx), but guessed it might trouble for the normal use (I'm pretty new to CentOS, although many experiences with Debian/Ubuntu). Is there any good tricks (or caveats) when moving users' home directory cleanly with CentOS? (I'm with CentOS 5.5 x86_64) Cheers, Soo-Hyun

15 16

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