From: Rost, Werner (Werner.Rost@zfboge.com)
Date: Wed Sep 18 2002 - 10:56:54 EDT
Does anyone run squidGuard on TRU64 5.1?
Though I had 19 nervous breakdowns I do not get it to run.
I had asked in the squidguadr-newsgroup but did not get
hints that really helped.
Environment: ALPHA XP1000
OS: TRU64 5.1A patchkit 2
According the SquidGuard instructions I installed
BerkeleyDb2.7.7 and SquidGuad 1.2.0. Installation looked
fine, but tests did not work.
$ echo "http://www.sex.de 10.10.10.10/- - GET" | /usr/local/bin/squidGuard
-c
/usr/local/squidGuard/filter.conf -d
2002-09-16 09:16:18 [23516] init domainlist
/usr/local/squidGuard/db/porn/domains
2002-09-16 09:16:18 [23516] loading dbfile
/usr/local/squidGuard/db/porn/domains.db
2002-09-16 09:16:18 [23516] domainlist empty, removed from memory
2002-09-16 09:16:18 [23516] init urllist /usr/local/squidGuard/db/porn/urls
2002-09-16 09:16:18 [23516] loading dbfile
/usr/local/squidGuard/db/porn/urls.db
2002-09-16 09:16:18 [23516] urllist empty, removed from memory
2002-09-16 09:16:18 [23516] squidGuard 1.2.0 started (1032160578.107)
2002-09-16 09:16:18 [23516] squidGuard ready for requests (1032160578.109)
2002-09-16 09:16:18 [23516] squidGuard stopped (1032160578.109)
I guess this test looks not very good because of the messages
"...list empty, removed from memory".
Some guys told me to use BerkelyDB 3.2.9 despite the SquidGuard
installation guidelines.
I did it:
1. delete directory /usr/local/BerkelyDB.3.2
and /usr/local/db-3.2.9
--> no Berkely* -Directories and no db-*Directories
exist anymore
2. cd /usr/local/squidGuard-1.2.0
make clean
3. Create directory /usr/local/db-3.2.9
# gunzip db_3.2.9.tar.gz
# tar -xf db_3.2.9.tar
4. Install the two patches
# pwd
/usr/local/db-3.2.9
# ls -l db_pat*
-rw-r--r-- 1 root users 2139 Sep 18 09:04 db_patch.3.2.9.1
-rw-r--r-- 1 root users 495 Sep 18 09:04 db_patch.3.2.9.2
#
# patch -p0 < db_patch.3.2.9.1
Hmm... Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
|*** include/log.h.orig 2001/01/25 18:22:51 11.20
|--- include/log.h 2001/02/06 05:02:28 11.21
--------------------------
Patching file include/log.h using Plan A...
Hunk #1 succeeded at 198.
Hmm... The next patch looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
|*** log/log.c.orig 2001/01/25 18:22:55 11.43
|--- log/log.c 2001/02/06 05:02:28 11.44
--------------------------
Patching file log/log.c using Plan A...
Hunk #1 succeeded at 309.
Hunk #2 succeeded at 385.
Hunk #3 succeeded at 414.
Hunk #4 succeeded at 424.
done
#
# patch -p0 < db_patch.3.2.9.2
Hmm... Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
|*** log/log_rec.c.orig 2001/01/25 18:22:56 11.49
|--- log/log_rec.c 2001/02/07 22:17:46
--------------------------
Patching file log/log_rec.c using Plan A...
Hunk #1 succeeded at 404.
Hmm... Ignoring the trailing garbage.
done
#
5. Configure + make db
# cd /usr/local/db-3.2.9/build_unix
# ../dist/configure
# make
# make install
see appending logfile db_configure.txt
=========================================================
Now BerkeleyDB is installed
There exists a directory /usr/local/BerkeleyDB.3.2
=========================================================
6. ldconfig
Using OS TRU64 5.1A there is no command ldconfig
nor exists a file /etc/ld.so.conf
Therefore I skip these recommended steps.
Seems this command is for linux guys.
7. Creating the SqudiGuard-Directory
# pwd
/usr/local
# tar -xf squidGuard-1.2.0.tar
#
8a. Configure SquidGuard using the Standard C-Compiler
cd /usr/local/squidGuard-1.2.0
./configure --with-db-lib=/usr/local/BerkeleyDB.3.2/lib \
--with-sg-config=/usr/local/squidGuard/filter.conf
checking for gcc... no
checking for cc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking how to run the C preprocessor... cc -E
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... ./install-sh -c
checking for bison... no
checking for byacc... no
checking for flex... flex
checking for yywrap in -lfl... no
checking for yywrap in -ll... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for lynx... false
checking for perl... /usr/bin/perl
checking for db_version in -ldb... no
** The Berkley DB library is required for squidGuard
to compile. Get it from http://www.sleepycat.com
use --with-db=DIR or --with-db-lib=DIR to specify
its location. (default is /usr/local/BerkeleyDB)
No Makefile / Makefile.in are built.
---> see appending C_config.log
8b. Configure SquidGuard using the GNU GCC-Compiler 3.0
cd /usr/local/squidGuard-1.2.0
(setenv CC "/usr/local/bin/gcc"; setenv CFLAGS "-O3"; \
./configure --with-sg-config=/usr/local/squidGuard/filter.conf \
--with-db=/usr/local/BerkeleyDB.3.2)
checking for gcc... /usr/local/bin/gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/local/bin/gcc accepts -g... yes
checking how to run the C preprocessor... /usr/local/bin/gcc -E
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... ./install-sh -c
checking for bison... no
checking for byacc... no
checking for flex... flex
checking for yywrap in -lfl... no
checking for yywrap in -ll... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for lynx... false
checking for perl... /usr/bin/perl
checking for db_version in -ldb... yes
checking for ANSI C header files... yes
checking for db.h... yes
checking for regex.h... yes
checking for unistd.h... yes
checking for /usr/local/bin/gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... (cached) yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for regcomp... yes
checking for regerror... yes
checking for regexec... yes
checking for strdup... yes
checking for strerror... yes
checking for vsprintf... yes
checking for sigaction... yes
checking for signal... yes
checking for regexec... yes
checking for strdup... yes
checking for strerror... yes
checking for vsprintf... yes
checking for sigaction... yes
checking for signal... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/sg.h
config.status: creating doc/Makefile
config.status: creating test/Makefile
config.status: creating test/test1.conf
config.status: creating test/test2.conf
config.status: creating samples/Makefile
config.status: creating samples/sample.conf
config.status: creating samples/squidGuard.cgi
config.status: creating samples/squidGuard-simple.cgi
config.status: creating contrib/Makefile
config.status: creating contrib/squidGuardRobot/squidGuardRobot
config.status: creating contrib/sgclean/sgclean
config.status: creating contrib/hostbyname/hostbyname
config.status: creating src/config.h
Makefile + Makefile.in are created
see appending GCC_config.log
9. make squidGuard
# pwd
/usr/local/squidGuard-1.2.0
# make
making all in squidGuard-1.2.0
making all in src
/usr/local/bin/gcc -I.. -I. -I. -I/usr/local/BerkeleyDB.3.2/include
-DHAVE_CONFI
G_H -O3 -I/usr/local/BerkeleyDB.3.2/include -c main.c
In file included from main.c:19:
sg.h:195: parse error before "DB_INFO"
sg.h:195: warning: no semicolon at end of struct or union
sg.h:201: parse error before '}' token
*** Exit 1
Stop.
*** Exit 1
Stop.
#
> Mit freundlichen Grüßen / regards
> Werner Rost
>
> ---------------------------------------------------------------------
> ZF Boge GmbH
> Werner Rost
> IT
> Friesdorfer Str. 175
> D-53175 Bonn
>
>
> phone: +49/228/3825 420
> fax: +49/228/3825 398
> werner.rost@zfboge.com
>
> www.boge-vibrationcontrol.com
> ---------------------------------------------------------------------
>
>
---------------------------------------------------------
This Mail has been checked for Viruses
Attention: Encrypted mails can NOT be checked!
**
Diese Mail wurde auf Viren geprueft
Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden!
---------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:53 EDT