Discuss June 2010

discuss@lists.centos.org

249 participants
188 discussions

Centos to use two ISP concurrently..?
by Roland RoLaNd 28 Jun '10

28 Jun '10

Hi all, I'm currently getting my Centos working as a proxy (squid) on a 2 Mb bandwidth plan that's serving 20 users. it's all good though our need for speed is increasing by the day. soon enough i'll be serving up to 60 user, hence the need to get higher bandwidth though here where the problem is. as i'm using HDSL, 2 Mb is the highest plan available. hence, i need to get 2 HDSL subscriptions, in other words 2 modems/IPs to work with.. ( 2 x 2 Mb) the possibility to use routing table isn't feasible as these two ISP's would only be used for browsing, so routing destinations one way or the other isn't an option. i have two initial thoughts to solve this hope you could straighten me out if they're wrong or suggest something better that your experience lead you to use: 1. setup Openvz on a centos box, get two templates up and running with squid setup on them. each one with a different IP. Each template would be routed to one ISP, and both proxies would be used in child/parent proxy manner so i could use caching from both. and i could split my users in half, 1 half would be using Squid#1 and the other using squid#2. 2. the same squid box have two Nics, with two IPs, one routed to each ISP, i get squid listening to port " 80" on both IPs, and same as above, half of my users would be running on IP#1 and the others on IP#2. do all this make any sense? i'm seeking your help as both ideas does not seem very professional to me, and i doubt that's the optimal solution so any help would be greatly appreciated. thanks , --Roland _________________________________________________________________ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969

6 6

wine 1.2 on centos
by Janez Kosmrlj 28 Jun '10

28 Jun '10

Hi, Has anyone tried the latest wine 1.2 RC on CentOS 5.5. We have some applications that don't work with the latest stable release. They require at least 1.1.34, but i would like to try 1.2. If someone has tried 1.2 on centos. Do you have build packages somewhere where i can get them? Regards, Janez

1 1

Stop auditd logging all commands
by Jorge Fábregas 28 Jun '10

28 Jun '10

Hello everyone, I have this box where auditd is logging every command typed on the system onto: /var/log/audit/audit.log Every line looks like: type=USER_TTY msg=audit msg=audit(124433....<snip> msg="command here" ... The strange thing is that I have other similar boxes and I don't see this behavior. I don't see any option in /etc/audit/* or any PAM module triggering it. Is there a way to stop this? I don't want to stop the service since "setroubleshoot" needs it. Any ideas? Thanks! Jorge

1 0

Announce list digest ??
by Ron Loftin 27 Jun '10

27 Jun '10

I have just noticed that the main CentOS list ( this list ) is no longer receiving the digest from the CentOS-Announce list. This appears to have stopped about a month ago. Did I miss a notification that this practice would be discontinued, or has something broken? I admit it took me a month to notice that it's been missing, but I did like to see the update notifications in digest form here. -- Ron Loftin reloftin(a)twcny.rr.com "God, root, what is difference ?" Piter from UserFriendly

1 0

Centos 5.5 on a Toshiba Satellite L1500D - Wireless networking - Realtek 8172
by Frank Cox 27 Jun '10

27 Jun '10

I just installed Centos 5.5 x86_64 on a new Toshiba Satellite L1500D. Everything seems to work (so far) other than the wireless networking; lscpi tells me: 0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. Unknown device 8172 (rev 10) I discovered that I need the realtek driver, so I found and downloaded these: rtl8192se_linux_2.6.0010.1012.2009_64bit.tar.gz rtl8192se_linux_2.6.0017.0507.2010.tar.gz The version dated 2010 appears to be newer, but I can't find one of them that says "64bit" so I'm not sure if I can actually use it or not. I un-tarred it into /usr/src, then copied the contents of the firmware directory to /lib/firmware. When I try to run the make command I get this error. I get the same error regardless of which of the two driver archives I use. What am I doing wrong? Is there an easier way to get this working? [root@localhost ~]# cd /usr/src/rtl8192se_linux_2.6.0017.0507.2010/ [root@localhost rtl8192se_linux_2.6.0017.0507.2010]# make make[1]: Entering directory `/usr/src/kernels/2.6.18-194.3.1.el5-x86_64' CC [M] /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/rtl_core.o In file included from /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/../../rtllib/rtl819x_TS.h:21, from /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/../../rtllib/rtllib.h:48, from /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/rtl_core.h:51, from /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/rtl_core.c:47: /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/../../rtllib/rtl819x_Qos.h:60: error: redeclaration of enumerator ‘false’ include/linux/stddef.h:16: error: previous definition of ‘false’ was here /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/../../rtllib/rtl819x_Qos.h:60: error: redeclaration of enumerator ‘true’ include/linux/stddef.h:18: error: previous definition of ‘true’ was here /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/../../rtllib/rtl819x_Qos.h:60: error: conflicting types for ‘bool’ include/linux/types.h:36: error: previous declaration of ‘bool’ was here /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/rtl_core.c: In function ‘rtl8192_pci_probe’: /usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/rtl_core.c:5542: warning: assignment discards qualifiers from pointer target type make[2]: *** [/usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192/rtl_core.o] Error 1 make[1]: *** [_module_/usr/src/rtl8192se_linux_2.6.0017.0507.2010/HAL/rtl8192] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.18-194.3.1.el5-x86_64' make: *** [all] Error 2 [root@localhost rtl8192se_linux_2.6.0017.0507.2010]# -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

5 8

Fwd: Install the 389 directory server error
by sync 26 Jun '10

26 Jun '10

Hi ,all : When I install the 389 ds today , there is a very strange thing on installing it . Please see the following messages, by the way , I installed the 389 ds version is 1.1.3 via the rpm packages: [root@foo dirsrv]# setup-ds-admin.pl ============================================================================== This program will set up the 389 Directory and Administration Servers. It is recommended that you have "root" privilege to set up the software. Tips for using this program: - Press "Enter" to choose the default and go to the next screen - Type "Control-B" then "Enter" to go back to the previous screen - Type "Control-C" to cancel the setup program Would you like to continue with set up? [yes]: ============================================================================== BY SETTING UP AND USING THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE LICENSE.TXT FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, PLEASE DO NOT SET UP OR USE THIS SOFTWARE. Do you agree to the license terms? [no]: yes ============================================================================== Your system has been scanned for potential problems, missing patches, etc. The following output is a report of the items found that need to be addressed before running this software in a production environment. 389 Directory Server system tuning analysis version 10-AUGUST-2007. NOTICE : System is x86_64-unknown-linux2.6.18-128.7.1.el5 (2 processors). WARNING: 994MB of physical memory is available on the system. 1024MB is recommended for best performance on large production system. NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds (120 minutes). This may cause temporary server congestion from lost client connections. WARNING: There are only 1024 file descriptors (hard limit) available, which limit the number of simultaneous connections. WARNING: There are only 1024 file descriptors (soft limit) available, which limit the number of simultaneous connections. Would you like to continue? [no]: yes ============================================================================== Choose a setup type: 1. Express Allows you to quickly set up the servers using the most common options and pre-defined defaults. Useful for quick evaluation of the products. 2. Typical Allows you to specify common defaults and options. 3. Custom Allows you to specify more advanced options. This is recommended for experienced server administrators only. To accept the default shown in brackets, press the Enter key. Choose a setup type [2]: ============================================================================== Enter the fully qualified domain name of the computer on which you're setting up server software. Using the form <hostname>.<domainname> Example: eros.example.com. To accept the default shown in brackets, press the Enter key. Computer name [foo]: The hostname foo does not look like a fully qualified host and domain name. If you feel you have made a mistake, please go back to this dialog and enter another name. ============================================================================== The servers must run as a specific user in a specific group. It is strongly recommended that this user should have no privileges on the computer (i.e. a non-root user). The setup procedure will give this user/group some permissions in specific paths/files to perform server-specific operations. If you have not yet created a user and group for the servers, create this user and group using your native operating system utilities. System User [nobody]: System Group [nobody]: ============================================================================== Server information is stored in the configuration directory server. This information is used by the console and administration server to configure and manage your servers. If you have already set up a configuration directory server, you should register any servers you set up or create with the configuration server. To do so, the following information about the configuration server is required: the fully qualified host name of the form <hostname>.<domainname>(e.g. hostname.example.com), the port number (default 389), the suffix, the DN and password of a user having permission to write the configuration information, usually the configuration directory administrator, and if you are using security (TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port number (default 636) instead of the regular LDAP port number, and provide the CA certificate (in PEM/ASCII format). If you do not yet have a configuration directory server, enter 'No' to be prompted to set up one. Do you want to register this software with an existing configuration directory server? [no]: ============================================================================== Please enter the administrator ID for the configuration directory server. This is the ID typically used to log in to the console. You will also be prompted for the password. Configuration directory server administrator ID [admin]: Password: Password (confirm): ============================================================================== The information stored in the configuration directory server can be separated into different Administration Domains. If you are managing multiple software releases at the same time, or managing information about multiple domains, you may use the Administration Domain to keep them separate. If you are not using administrative domains, press Enter to select the default. Otherwise, enter some descriptive, unique name for the administration domain, such as the name of the organization responsible for managing the domain. Administration Domain [foo]: ============================================================================== The standard directory server network port number is 389. However, if you are not logged as the superuser, or port 389 is in use, the default value will be a random unused port number greater than 1024. If you want to use port 389, make sure that you are logged in as the superuser, that port 389 is not in use. Directory server network port [389]: ============================================================================== Each instance of a directory server requires a unique identifier. This identifier is used to name the various instance specific files and directories in the file system, as well as for other uses as a server instance identifier. Directory server identifier [foo]: ============================================================================== The standard directory server network port number is 389. However, if you are not logged as the superuser, or port 389 is in use, the default value will be a random unused port number greater than 1024. If you want to use port 389, make sure that you are logged in as the superuser, that port 389 is not in use. Directory server network port [389]: ============================================================================== Each instance of a directory server requires a unique identifier. This identifier is used to name the various instance specific files and directories in the file system, as well as for other uses as a server instance identifier. Directory server identifier [foo]: ============================================================================== The standard directory server network port number is 389. However, if you are not logged as the superuser, or port 389 is in use, the default value will be a random unused port number greater than 1024. If you want to use port 389, make sure that you are logged in as the superuser, that port 389 is not in use. Directory server network port [389]: ============================================================================== Each instance of a directory server requires a unique identifier. This identifier is used to name the various instance specific files and directories in the file system, as well as for other uses as a server instance identifier. Directory server identifier [foo]: Why is it become that? Could someone give me some suggestions? Thanks in advance~

2 2

Using CentOS on commercial product.
by Shinobu Takasugi 26 Jun '10

26 Jun '10

Hello, I've sent this mail when I didn't subscribe this mailing list. Now I subscribe and I sent again. I'm sorry to bother you. Our company make and sell some measurement system controlled by PC. We use Red Hat Enterprise Linux on the PC currently. We are thinking CentOS is another option for us. There is no technical issue but we don't have enough information about license. We will do the following, 1) Install CentOS and our applications on the PC. 2) Sell the PC to our customer. 3) Distribute DVD made from CentOS iso image file to our customer. Question 1 Is there no problem from the view point of CentOS license? Question 2 Should we donate to CentOS community? In FAQ http://www.centos.org/modules/smartfaq/faq.php?faqid=49, there is a description concerning donation when CentOS is used for business. ------------------------------------------------------------------------- If CentOS is the basis of your business, you should also consider making monthly donations to the CentOS Project, or even providing a dedicated server for our use. ------------------------------------------------------------------------- Best Regards, Shinobu Takasugi --

4 4

Re: [CentOS] [CentOS-virt] KVM with bridge in one interface
by James B. Byrne 25 Jun '10

25 Jun '10

I am having a couple of iptables issues with this type of setup myself. The RH manual says to insert a rule into the FORWARD chain like this: -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT However, for the host does this not mean that every packet is accepted. As far as I can discern from the documentation, when one sets up a physically bridged network on a kvm host then every packet arrives across the bridge interface and, insofar as the host is concerned, anything that it does not orginate itself is forwarded. I may be wrong on this, but the behaviour of my ssh filters since putting that command in the FORWARD chain indicates that something along those lines is occurring. The i/f eth0 seems to have no relevence to iptables rules for the host instance. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 1

Resize all partitions bigger
by Robert Arkiletian 25 Jun '10

25 Jun '10

I effectively have 1 drive /dev/sda (it's actually a hardware raid 10 array) I have lots of free sapce. I want to resize my partitions (boot, home, /) bigger. Going to use Clonezilla to make an image of each partition and save it on another box. Then re-partition and format new bigger partitions. Then restore images with Clonezilla. But I know UUID's will be wrong and I don't feel like creating new ones. I just want to use /dev/sdx Am I correct in assuming I only need to edit /etc/fstab and /etc/grub.conf or is there anything else I need to edit? Thanks -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada

4 5

Using CentOS Live CD to recover trashed RHEL system
by drew einhorn 25 Jun '10

25 Jun '10

Hi, There's a RHEL5 system somewhere across the internet with a trashed root file system. I have VPN access to the subnet where it lives. But the system is not talking to the network. The current plan is having an onsite person boot from a CentOS Live CD, copy a small script to configure networking, set a password for the centos user, start sshd, and tweak the default firewall to allow incoming ssh connections, once I have remote access to the live cd environment I'll create a new lvm logical volume, create a file system, and restore from a level 0 dump taken from a lvm snapshot just before things broke. I'm pretty confident I have all of the above under control. The part I'm not certain about is the grub voodoo to get the system to boot to the lvm with the restored root file system. I'm not certain of the vintage of the restored root file system it was built from an old RHEL5 installation cd and last updated a year or so ago. I have a CentOS 5.5 live cd .iso image staged for the onsite person to burn. Are there differences in the boot process for CentOS/RHEL 5.x versions that I have to worry about. Would it be better to try to get a closer match between the root file system and the live cd vintages. At the moment I'm googling for info on the grub incantations for changing the root file system logical volume. Any comments suggestions would be appreciated. Thanks, -- Drew Einhorn "You can see a lot by just looking." -- Yogi Berra

3 3

← Newer
1
2
3
4
5
6
7
8
...
19
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2010