From owner-freebsd-database Mon Jun 12 0:58:21 2000 Delivered-To: freebsd-database@freebsd.org Received: from hotmail.com (f297.law8.hotmail.com [216.33.240.172]) by hub.freebsd.org (Postfix) with SMTP id 7762F37BBFC for ; Mon, 12 Jun 2000 00:58:17 -0700 (PDT) (envelope-from jmd526@hotmail.com) Received: (qmail 14553 invoked by uid 0); 12 Jun 2000 07:58:17 -0000 Message-ID: <20000612075817.14552.qmail@hotmail.com> Received: from 209.220.228.2 by www.hotmail.com with HTTP; Mon, 12 Jun 2000 00:58:17 PDT X-Originating-IP: [209.220.228.2] From: "John Daniels" To: freebsd-database@freebsd.org Subject: Installing Postgresql v7.0.2 with the v7.0.0 port Date: Mon, 12 Jun 2000 03:58:17 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: This email explains what I had to do to modify the v7.0.0 port so that it would install v7.0.2. I am running 4.0-STABLE. My make command was: "make -DWITH_TCL -DWITH_JDBC". 1) Makefile: I changed "7.0.0" to "7.0.2" 2) Makefile: I commented out the line: "${INSTALL_MAN} ${WRKDIR}/${DISTNAME}/doc/*ps.gz ${PREFIX}/share/doc/ pgsql" because v7.0.2 has no .ps.gz files (see #3) 3) PLIST.doc: I deleted all lines for .ps.gz documents: share/doc/pgsql/admin.ps.gz share/doc/pgsql/adminA4.ps.gz share/doc/pgsql/programmer.ps.gz share/doc/pgsql/programmerA4.ps.gz share/doc/pgsql/tutorial.ps.gz share/doc/pgsql/tutorialA4.ps.gz share/doc/pgsql/user.ps.gz share/doc/pgsql/userA4.ps.gz I assume that ".ps" indicates postscript files and that that form of documentation has been discontinued. 4) I changed the MD5 file to include the correct file names and checksums by commenting out the lines that were there and adding the following lines: "MD5 (postgresql/postgresql-7.0.2.base.tar.gz) = 871d23b85d9a3599a7ed75dfc7da7ba7" "MD5 (postgresql/postgresql-7.0.2.docs.tar.gz) = efac1f87463f252e54d72b256885b883" "MD5 (postgresql/postgresql-7.0.2.support.tar.gz) = c21180a6485d85785c8e69f0cbff05dd" "MD5 (postgresql/postgresql-7.0.2.tar.gz) = fc512e38394256e2749299fdd69a937e" "MD5 (postgresql/postgresql-7.0.2.test.tar.gz) = 3443b3d83194c396f20aee2adc6f93bf" (NOTE I added quote marks, they should not appear in the file.) 5) patch-bb: I changed the following line: "CFLAGS+= -I$(SRCDIR)/include -I$(SRCDIR)/backend" - to - "CFLAGS+= -I$(SRCDIR)/include -I$(SRCDIR)/backend $(PGSQL_INCLUDES)" 6) ** CAUTION ** First, I am not the port maintainer, so I can't say that these changes are correct or that they are the only changes. I was not able to obtain a list of file changes (adds, deletes), so I cannot say that the file lists in the PLIST files are correct. I am not very familiar with ports or Postgresql and I have done limited testing. ANY USE OF THE ABOVE CHANGES IS AT YOUR OWN RISK! I would *strongly* suggest that you install v7.0.0 or wait for the port maintainer to officially upgrade the port (about three weeks from now) if at all possible. 7) ERRATA The next time the port is updated, the following should be taken into account: Tcl/Tk is now at version 8.3.1. Java 2 (JDK 1.2.2) ports are now available on FreeBSD. The current port only allows for use with JDK 1.1.8. John ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message From owner-freebsd-database Tue Jun 13 0:32:50 2000 Delivered-To: freebsd-database@freebsd.org Received: from www.walshsimmons.co.uk (www.walshsimmons.co.uk [194.200.209.2]) by hub.freebsd.org (Postfix) with ESMTP id 1965137BAB6 for ; Tue, 13 Jun 2000 00:32:44 -0700 (PDT) (envelope-from paul@walshsimmons.co.uk) Received: from cesar.nationnet.com (mag.nation-net.com [194.200.209.123]) by www.walshsimmons.co.uk (8.8.8/8.8.8) with SMTP id IAA11259 for ; Tue, 13 Jun 2000 08:41:21 +0100 (BST) From: "Paul Walsh" To: Subject: FW: Thread issues on FreeBSD 3.4/4.0 with MySQL Date: Tue, 13 Jun 2000 08:32:23 +0100 Message-ID: <015301bfd509$848b3200$7bd1c8c2@nationnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Could anybody comment on the following - we are trying to get a pretty busy MySQL server optimised on FreeBSD4.0 having switched from 3.4 after reading on the MySQL list: "if decide to go with FreeBSD, be sure to install the latest 4.0 release as 3.x releases had quite some problems with thread libraries. " and receiving the comments below from Scott Hess Regards, Paul Walsh WALSH SIMMONS The Old Bank, 247 Chapel St, Manchester, UK T:01618399337 F:01618399336 ISDN:01618346884 www.walshsimmons.co.uk Paul mobile: 07714 523312 -----Original Message----- From: Scott Hess [mailto:scott@avantgo.com] Sent: 01 June 2000 18:38 To: Paul Walsh Cc: mysql@lists.mysql.com Subject: RE: Thread problems on FreeBSD 3.4 Hmm, have you done any tests regarding the maximum transactions per second you can push through the database, as measured by iostat? We found that our database performance did not scale with our disk performance, but we really didn't realize how bad it was until we installed a 6-disk RAID array and only saw perhaps %25 performance improvement. Some simple custom test scripts showed 5x performance improvements for similar access patterns. With multiple MySQL daemons running off of the same tables, we were able to realize about 3x performance compared to running a single one. [NOTE: This is on the RAID array, on a single disk we saw nowhere near that improvement.] The basic problem is that the current FreeBSD pthreads implementation makes disk I/O seek-bound and having multiple spindles doesn't help because it can only do a single seek at a time. I'm aware of nothing in FreeBSD4.x that fixes this, though there is work in 5.x that may address the problem. I've also done some modifications to the pthreads library to temporarily fix the problem, but haven't been able to get the patch to production quality, yet. Later, scott On Thu, 1 Jun 2000, Paul Walsh wrote: > We have just installed FreeBSD 4/MySQL 3.22.32 and it is a lot better - > there is more free memory too. > > Scott Hess [mailto:scott@avantgo.com] wrote: >> On Thu, 25 May 2000, Paul Walsh wrote: >> > Are there thread problems / issues on FreeBSD with busy MYSQL >> > servers? >> > >> > Any pointers to documentation/fixes/optimisations for this? >> >> FreeBSD's threading library is implemented such that you cannot have >> multiple pending disk I/O requests. This can limit MYSQL's >> performance, especially on fast hardware (aka RAID arrays). You can >> run multiple MYSQL instances on different ports against the same data >> files to partially address this. _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre. For further information visit http://www.star.net.uk/stats.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message From owner-freebsd-database Tue Jun 13 10: 7:47 2000 Delivered-To: freebsd-database@freebsd.org Received: from iencentral.com (mail.iencentral.com [204.85.34.194]) by hub.freebsd.org (Postfix) with ESMTP id 6EE5837B7ED for ; Tue, 13 Jun 2000 10:07:42 -0700 (PDT) (envelope-from dbrooks@iencentral.com) Received: from ouch (firewall.iencentral.com [204.85.34.195]) by iencentral.com (8.9.3/8.9.3) with SMTP id NAA49122 for ; Tue, 13 Jun 2000 13:07:41 -0400 (EDT) (envelope-from dbrooks@iencentral.com) Message-ID: <00ae01bfd559$7e1e8c00$0405010a@office.iencentral.com> From: "David E. Brooks Jr" To: Subject: Consultant claims Oracle client library for FreeBSD. Is this true? Date: Tue, 13 Jun 2000 13:04:53 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AB_01BFD537.F6E3B920" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00AB_01BFD537.F6E3B920 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I just got out of a meeting where an Oracle consultant claimed that = client libraries for FreeBSD were available. Has anyone heard of such a = beast or (better yet) have any experience with it? Thanks much, -- Dave -- David E. Brooks Jr iEntertainment Network ------=_NextPart_000_00AB_01BFD537.F6E3B920 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I just got out of a meeting where an = Oracle=20 consultant claimed that client libraries for FreeBSD were = available.  Has=20 anyone heard of such a beast or (better yet) have any experience with=20 it?
 
Thanks much,
 
-- Dave
 
--
David E. Brooks = Jr
iEntertainment=20 Network
------=_NextPart_000_00AB_01BFD537.F6E3B920-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message From owner-freebsd-database Tue Jun 13 11:45:31 2000 Delivered-To: freebsd-database@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id AA74237C0A8 for ; Tue, 13 Jun 2000 11:45:27 -0700 (PDT) (envelope-from berend@pobox.com) Received: from auke.nederware.nl (nederware.nl [194.109.55.62]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA23236 for ; Tue, 13 Jun 2000 20:45:24 +0200 (CEST) Received: from bmach (bmach.nederware.nl [192.168.33.3]) by auke.nederware.nl (8.8.8/8.8.8) with SMTP id UAA26834 for ; Tue, 13 Jun 2000 20:16:48 +0200 (CEST) (envelope-from berend@pobox.com) From: "Berend de Boer" To: Subject: RE: Thread issues on FreeBSD 3.4/4.0 with MySQL Date: Tue, 13 Jun 2000 20:16:46 +0200 Message-ID: <00cc01bfd563$8989eee0$0321a8c0@bmach.nederware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <015301bfd509$848b3200$7bd1c8c2@nationnet.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could anybody comment on the following - we are trying to get > a pretty busy > MySQL server optimised on FreeBSD4.0 having switched from 3.4 > after reading > on the MySQL list: Have you tried some other database to see if they're suspectable to the same thing? Maybe a different architecture helps a lot. I don't have the idea that the MySQL guys understand much of databases. InterBase is free these days. I tried to run version 6, but I missed some libraries so I gave up, have to retry one of these days. You can try it yourself, or try Oracle or so, just to see what happens. Groetjes, Berend. (-: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message From owner-freebsd-database Tue Jun 13 15:54:15 2000 Delivered-To: freebsd-database@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id AAD1737B6D1 for ; Tue, 13 Jun 2000 15:54:10 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id QAA20965 for ; Tue, 13 Jun 2000 16:55:59 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Tue, 13 Jun 2000 16:55:59 -0600 (CST) From: Ryan Thompson To: freebsd-database@freebsd.org Subject: Securing Perl::DBI connections Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have several mySQL users @localhost who have various privileges on various databases. While no outside hosts are allowed to connect to mySQL (and I have even blocked the ports on our uplink firewall), there is a small chance that a user with local telnet access could discover passwords for a few of the databases that our backend Perl applications use. There is no really sensitive information up for grabs, but I *do* want to keep things secure, if for no other reason than to ensure the integrity of the databases. The problem lies in the storage of passwords. Automated programs need to store the password. And, when we're talking about a world-readable clear-text Perl program, we're talking about clear-text passwords. Now, I could beef up permissions somewhat, but since most of these programs run under Apache, they must be executable by "nobody". FWIW, I don't store passwords in the programs themselves, just the support modules which exist elsewhere on the system (completely off of our web tree). Any ideas on how I could ensure that only a few of my programs can have access to a mySQL database, without putting the password clear-text for anyone with a shell account to see? - Ryan -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message From owner-freebsd-database Tue Jun 13 17:36:48 2000 Delivered-To: freebsd-database@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id A60D937BD06 for ; Tue, 13 Jun 2000 17:36:46 -0700 (PDT) (envelope-from jasone@magnesium.net) Received: (qmail 40642 invoked by uid 1142); 14 Jun 2000 00:36:46 -0000 Date: 13 Jun 2000 17:36:46 -0700 Date: Tue, 13 Jun 2000 17:36:10 -0700 From: Jason Evans To: Paul Walsh Cc: freebsd-database@freebsd.org Subject: Re: FW: Thread issues on FreeBSD 3.4/4.0 with MySQL Message-ID: <20000613173610.J47268@blitz.canonware.com> References: <015301bfd509$848b3200$7bd1c8c2@nationnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <015301bfd509$848b3200$7bd1c8c2@nationnet.com>; from paul@walshsimmons.co.uk on Tue, Jun 13, 2000 at 08:32:23AM +0100 Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 13, 2000 at 08:32:23AM +0100, Paul Walsh wrote: > Hi > > Could anybody comment on the following - we are trying to get a pretty busy > MySQL server optimised on FreeBSD4.0 having switched from 3.4 after reading > on the MySQL list: > > "if decide to go with FreeBSD, be sure to install the latest 4.0 > release as 3.x releases had quite some problems with thread libraries. " > > and receiving the comments below from Scott Hess Scott's comments bring up a definite issue with FreeBSD's libc_r with regard to databases. libc_r is a userland library that does call conversion to avoid blocking in the kernel. Unfortunately, this isn't possible for "fast devices", which is what hard drives are considered. There isn't a good fix for this in libc_r; it's a design limitation of userland threading. There is another option, however. There is the linuxthreads port, which is a port of the LinuxThreads package normally associated with GNU libc. This threads package uses clone() (actually a special form of rfork() call on FreeBSD) to run one thread per process. With some tuning, you can probably make this threads package scale reasonably to multiple processors/disks. I've recently updated this port to the most recent released version of LinuxThreads. The port should be 100% compatible with LinuxThreads as they run on Linux, except that I did not take the time to make the gdb hooks work. As for the future, we're working on a replacement for libc_r that will be a first class threads implementation. This will probably be done for FreeBSD 5.0, but that doesn't help in the short term, which is why I recommend the linuxthreads port. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message