Discuss December 2005

discuss@lists.centos.org

219 participants
328 discussions

RE: [CentOS] Linking against a specific Berkeley DB install
by Bowie Bailey 01 Dec '05

01 Dec '05

From: Craig White [mailto:craigwhite@azapple.com] > > it's not linking against db4.4 only 4.2 and 4.3 as you can see above. > 4.4 was just released and clearly not tested and definitely not > recommended. You should note that even the latest 4.3 version isn't > recommended for use with openldap but rather 4.2.52+patches. Hmmm... 4.4.16 is the default download link on the website. I assumed that was the latest stable version. I was able to get OpenLDAP to compile against db4.3. Any particular reason it isn't recommended? Bowie

4 5

Default CentOS(Redhat) iptables, Secure?
by Mark Sargent 01 Dec '05

01 Dec '05

Hi All, whilst not being an expert on iptables, the below ouput of iptables -L seems too insecure to me. Does anyone agree.? Perhaps I'm not understanding it as well as I think I am.? Please give your thoughts on this. Cheers. Mark Sargent. [root@localhost racket]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED REJECT all -- anywhere anywhere reject-with icmp-host-prohibited You have new mail in /var/spool/mail/root

4 7

Linking against a specific Berkeley DB install
by Bowie Bailey 01 Dec '05

01 Dec '05

I sent this question to the OpenLDAP list yesterday, but I still haven't seen the message come across the list. I am asking here in the hopes of getting a faster response. I am trying to compile OpenLDAP 2.3.11 from source on CentOS4. I have the rpm for db4-4.2.52-7.1 installed and also a source build of BerkeleyDB in /usr/local/BerkeleyDB.4.4. How do I get OpenLDAP to link with the bdb 4.4? I have put the library locataion everywhere I can think of: LDFLAGS=-L/usr/local/BerkeleyDB.4.4/lib LD_LIBRARY_PATH=/usr/local/BerkeleyDB.4.4/lib LD_RUN_PATH=/usr/local/BerkeleyDB.4.4/lib Still, the configure seems to link with the 4.2 rpm build: checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for Berkeley DB link (default)... no checking for Berkeley DB link (-ldb43)... no checking for Berkeley DB link (-ldb-43)... no checking for Berkeley DB link (-ldb-4.3)... no checking for Berkeley DB link (-ldb-4-3)... no checking for Berkeley DB link (-ldb42)... no checking for Berkeley DB link (-ldb-42)... no checking for Berkeley DB link (-ldb-4.2)... yes checking for Berkeley DB version match... yes checking for Berkeley DB thread support... yes checking Berkeley DB version for BDB/HDB backends... yes Any suggestions? Bowie

3 3

test please ignore
by Nielsen, Steve 01 Dec '05

01 Dec '05

test message

3 2

Connecting to USBDISKs
by Edward Coyle 01 Dec '05

01 Dec '05

When trying to connect to my USBDISK I receive an error message that it is not supported.

2 1

RE: [CentOS] Linking against a specific Berkeley DB install
by Bowie Bailey 01 Dec '05

01 Dec '05

From: Will McDonald [mailto:wmcdonald@gmail.com] > > On 01/12/05, Will McDonald <wmcdonald(a)gmail.com> wrote: > > On 01/12/05, Bowie Bailey <Bowie_Bailey(a)buc.com> wrote: > > > > > > I am trying to compile OpenLDAP 2.3.11 from source on CentOS4. > > > I have the rpm for db4-4.2.52-7.1 installed and also a source > > > build of BerkeleyDB in /usr/local/BerkeleyDB.4.4. > > > > > > How do I get OpenLDAP to link with the bdb 4.4? > > > > Typically this would be done at the configure stage. Check... > > > > ./configure --help > > > > for OpenLDAP 2.3.11 for more information. > > Actually, ignore that. OpenLDAP doesn't appears to have any Berkley > DB specific options in its configure. I just downloaded it to have a > look. > > I'll try installing it here and see how far I get... I got a bit farther. As far as I can tell, OpenLDAP 2.3.11 doesn't like BerkleyDB 4.4. I was able to get it to configure against 4.3 using the following: export LDFLAGS="-L/usr/local/lib -L/usr/local/BerkeleyDB.4.3/lib -R/usr/local/lib -R/usr/local/BerkeleyDB.4.3/lib" export LD_LIBRARY_PATH=/usr/local/BerkeleyDB.4.3/lib export LD_RUN_PATH=/usr/local/BerkeleyDB.4.3/lib export CPPFLAGS="-I/usr/local/BerkeleyDB.4.3/include" Apparently, either the CPPFLAGS variable, or the '-R' entry in LDFLAGS made the difference. Hopefully, I won't run into any compilation issues now. If you find a way to compile it against BDB 4.4, let me know. Bowie

1 0

Konqueror Keeps Crashing
by Edward Coyle 01 Dec '05

01 Dec '05

Konqueror crashes reqularly and I would like to reinstall it. How do I reinstall KDE and/or Konqueror?

2 1

packages
by John Dangler 01 Dec '05

01 Dec '05

sorry for the newb questions, but I'm new to linux administration, and even newer to centOS. I do have some experience with Gentoo Linux. How can I get a list of packages that are installed in my system? Is there an equivalent of merge -uDvt world? (This updates the installed packages with latest releases) Is there an equivalent of portage in centOS? (The portage site lists all available packages for Gentoo by 'category'). Thanks for the help. JD

4 3

RE: [CentOS] Linking against a specific Berkeley DB install
by Bowie Bailey 01 Dec '05

01 Dec '05

From: Bowie Bailey > > I am trying to compile OpenLDAP 2.3.11 from source on > CentOS4. I have the rpm for db4-4.2.52-7.1 installed and also a > source build of BerkeleyDB in /usr/local/BerkeleyDB.4.4. > > How do I get OpenLDAP to link with the bdb 4.4? > > I have put the library locataion everywhere I can think of: > > LDFLAGS=-L/usr/local/BerkeleyDB.4.4/lib > LD_LIBRARY_PATH=/usr/local/BerkeleyDB.4.4/lib > LD_RUN_PATH=/usr/local/BerkeleyDB.4.4/lib > > Still, the configure seems to link with the 4.2 rpm build: > > checking db.h usability... yes > checking db.h presence... yes > checking for db.h... yes > checking for Berkeley DB link (default)... no > checking for Berkeley DB link (-ldb43)... no > checking for Berkeley DB link (-ldb-43)... no > checking for Berkeley DB link (-ldb-4.3)... no > checking for Berkeley DB link (-ldb-4-3)... no > checking for Berkeley DB link (-ldb42)... no > checking for Berkeley DB link (-ldb-42)... no > checking for Berkeley DB link (-ldb-4.2)... yes > checking for Berkeley DB version match... yes > checking for Berkeley DB thread support... yes > checking Berkeley DB version for BDB/HDB backends... yes Update... On the assumption that maybe OpenLDAP just doesn't like bdb 4.4, I built and installed bdb 4.3 and then tried the OpenLDAP build again. This time I get a different message: checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for Berkeley DB link (default)... no checking for Berkeley DB link (-ldb43)... no checking for Berkeley DB link (-ldb-43)... no checking for Berkeley DB link (-ldb-4.3)... yes checking for Berkeley DB version match... Berkeley DB version mismatch header: Sleepycat Software: Berkeley DB 4.2.52: (February 22, 2005) library: Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005) no configure: error: Berkeley DB version mismatch It seems like it is getting the header from the rpm install. I don't want to remove the rpm because of dependencies (Perl, Python, PAM, etc). Is there any way I can leave the old rpm in place and just compile OpenLDAP against the newer build? Thanks, Bowie

1 0

wait() fails
by Michael Ubell 01 Dec '05

01 Dec '05

I have a program that forks a child, sleeps for a while and then kills the child and waits for it. On CentOs (4) the wait sometimes fails with a "No child" error. I have not seen this on any other system. This program has been running for years on Solaris, older Redhat distributions, etc. I would say the failure rate is about 1 in 10. I put a breakpoint on the error and forced the code to wait again. It works the second time. Is this a known bug? Mike

2 2

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 December 2005