Wow! Thanks, Chris! I mis-spoke yesterday when I said that RH 7.2 came with an RPM version of Berkeley 3.3. My RH 7.1 installed <db3 3.1.17.rpm>, and with a quick glance I saw db 3.3. It's actually Berkeley db 3.1.17, and it is being used by a couple of other packages. I also have db 2.7.7 that I installed from a tar.gz, strictly for squidGuard.
The files for those two programs are located as follows: /usr/local/BerkeleyDB /usr/local/squidGuard /usr/local/src/db-2.7.7 /usr/local/src/squidGuard-1.1.4 Would you stay with that arrangement or would you change it? How do I get rid of the old versions without creating problems? (Way back there you could simply delete the directory...) Thanks again! Rick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Fletcher Sent: Thursday, March 07, 2002 10:21 AM To: Rick Matthews Cc: Schade Frank (sf); Squidguard Mailing List Subject: RE: how to update to 1.2 tar zxvf db-3.3.11.tgz cd db-3.3.11/build_unix ../dist/configure make make install cd ../.. echo /usr/local/BerkeleyDB.3.3/lib >> /etc/ld.so.conf ldconfig tar zxvf squidGuard-1.2.0.tar.gz cd squidGuard-1.2.0 ./configure --with-db=/usr/local/BerkeleyDB.3.3 make (Now either make install or copy the src binary to wherever you want it). If you want emergency mode to block by default rather than allow, edit the src/sgDiv.c file in squidGuard and change line 671 from: puts(""); to: puts("http://127.0.0.1/cgi-bin/emergency.cgi";); Copy your old squidGuard.conf file over. You cannot use the BerkeleyDB 2 files with Berkeley DB 3. If you are using DBs from the disk, rm *.db and do a squidGuard -d -C all On Thu, 7 Mar 2002, Rick Matthews wrote: > I think that's a great question to cover here - What is the correct > process for upgrading? (I haven't upgraded either.) How do you: > > Current: Upgrade to: > ---------------- ---------------- > Redhat 7.2 Redhat 7.2 > squidGuard 1.1.4 squidGuard 1.2 > Berkeley db 2.77 Berkeley db 3.3 > > squidGuard upgrade: > You guys that have upgraded - will the version 1.2 installation > realize that it is an upgrade and "take care of" the 1.1.4 > installation? Does it remove the 1.1.4 installation? (If it doesn't > remove the 1.1.4 installation, how is that done?) Are specific > instructions included for a clean upgrade? > > Berkeley db upgrade: > The Redhat 7.2 distribution includes Berkeley db 3.3 in an RPM, so > that installation is easy. In fact, I'm running RH 7.1 and I have db > 3.3 that was installed from RPM and db 2.77 that was installed from > a tar.gz. How would I "uninstall" the 2.77 version? It may be that > the squidGuard 1.2 compile will look and find the 3.3 version and be > fine. I'd still like to remove the 2.77 version; how is that done? > > Thanks in advance for your answers! > > Rick Matthews > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Schade > Frank (sf) > Sent: Thursday, March 07, 2002 12:14 AM > To: [EMAIL PROTECTED] > Subject: how to update to 1.2 > > > I'm running SquidGuard: 1.1.4, Berkeley DB 2.7.7 with > squid-2.4.STABLE1-6 on a redhat 7.2 box. > What I've have to do for upgrading to SG 1.2 (especially how to move > from Berkeley DB 2.7.7 to 3.x.) > Please give also common known details for I'm not familiar with > "make". > Thanks > Frank > >
