Discuss

discuss@lists.centos.org

34753 discussions

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

Hardware RAID 10 server - reformat NTFS partition to ext3 and resize for Centos 5.5
by Ed Westphal 25 Jun '10

25 Jun '10

Here's the situation. I have a dual boot machine - originally had Red Hat and Windows 2000 Pro. The NTFS partition never did seem to 'get along' with the Adaptec 2400A caching RAID controller. Linux always seemed to like the I2O drivers. I went from RH Enterprise to now running Centos 5.5. Works great! I really don't want the 200 gigs worth of NTFS. Can't I just run GParted from a CD, reformat the NTFS and append the space to the existing Linux partition? What will I have to do with LVM to see the expanded partion? - anything special? I've never done this before - is it really much more complicated than I've outlined here? Please advise this old simpleton. Many thanks in advance. Ed Westphal

2 1

Samba share configuration: r/w for some users, read-only for others
by Niki Kovacs 25 Jun '10

25 Jun '10

Hi, I'm using Samba for some basic setups like open shares for everybody, or restricted shares with Samba users and passwords. So far, everything works fine. I have two situations which both more or less amount to the same, and I don't know how to configure it. One is in a school, the other one in a town hall. 1) In the school, I'd like to configure a share that is readable and writable for all the teachers, and read-only for the students. The idea is that the teachers can write some assignments or various papers and then put them in the share so the students can access them (without modifying them). 2) Similar setup in the town hall. The mayor wants to have a share where he and his secretary can fully access the documents, write them and modify them, and the library users can then access them read-only. Is this feasible with Samba? And if so, what would the according smb.conf look like? Cheers from the sunny South of France, Niki

3 2

versioning file system for Linux
by Boris Epstein 25 Jun '10

25 Jun '10

Hi all, I would be nice if we could find a reliable versioning file system to use as an underlying revision control mechanism. Going by this http://en.wikipedia.org/wiki/Versioning_file_system there aren't all that many options but I am still hopeful. We would most likely be hosting it on a CentOS machine. If you have a perspective on this please share it. Thanks. Boris.

1 1

Bug in cfdisk?
by Niki Kovacs 24 Jun '10

24 Jun '10

Hi, I'm currently working through Sander Van Vugt's "Beginning the Linux Command Line" (Apress), just for fun. Right now I'm just trying out all the examples in chapter 5, dedicated to managing partitions and logical volumes. After some work with fdisk (which I normally use), the book introduces cfdisk (which I've been using in Slackware days). Curiously enough, CentOS' cfdisk doesn't seem to work. I'm experimenting with two USB sticks connected to an old NEC Powermate, which appear as /dev/sda resp. /dev/sdb. I can access them with fdisk OK and partition them any way I want. Except I can't seem to open them with cfdisk. When I try it, I get the following error message : ************************************** FATAL ERROR: Cannot seek disk on drive Press any key to exit cfdisk ************************************** Now I don't really mind about that error, since fdisk does anything I need. But I'm just wondering about why that happens. Any idea? Niki

2 1

problem rebuilding kvm package on centos 5.5
by David Mansfield 24 Jun '10

24 Jun '10

Hi All: I'm trying to rebuild the kvm SRPM (kvm-83-164.el5_5.9.src.rpm) on a centos 5.5 x86_64 and it's failing with the message: error: Failed build dependencies: kernel-devel-x86_64 = 2.6.18-194.el5 is needed by kvm-83-164.9.x86_64 I have already run "yum-builddep <srpm>" and here is the output (indicates nothing missing) Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * addons: mirror.highspeedweb.net * base: mirror.cogentco.com * epel: mirror.seas.harvard.edu * extras: mirror.skiplink.com * rpmforge: fr2.rpmfind.net * updates: mirrors.adams.net Excluding Packages from Extra Packages for Enterprise Linux 5 - x86_64 Finished Checking for new repos for mirrors SDL-devel-1.2.10-8.el5.x86_64 dev86-0.16.17-2.2.x86_64 iasl-20090123-1.el5.x86_64 zlib-devel-1.2.3-3.x86_64 gnutls-devel-1.4.1-3.el5_4.8.x86_64 texi2html-1.76-4.fc6.noarch rsync-3.0.7-1.el5.rf.x86_64 1:pkgconfig-0.21-2.el5.x86_64 pciutils-devel-2.2.3-8.el5_4.x86_64 qspice-libs-devel-0.3.0-54.el5.x86_64 kernel-devel-2.6.18-194.3.1.el5.x86_64 kernel-devel-2.6.18-194.el5.x86_64 No uninstalled build requires I can't figure how this missing dependency would be resolved?

4 5

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