Re: Postgesql and SSL

Hello again,

 nope, no use of it.. Situation stays the same.. Does any one have more
ideas?


--
Lukas
UAB nSoft
http://www.nsoft.lt
Lukas at nsoft.lt
+370 655 10 655


> You defo have all the required openssl headers and libs and configure
> succeeds? It's a longshot, but I wonder if the prefix is somehow making
> configure read the string wrong? I've never really needed to use prefix,
> but what happend if you try
>
> ./configure --prefix='/DB' --with-openssl
>
> or perhaps
>
> ./configure --with-openssl  --prefix=/DB
>
>
>
> --- On Sat, 28/2/09, Lukas <Lukas@fmf.vtu.lt> wrote:
>
>> From: Lukas <Lukas@fmf.vtu.lt>
>> Subject: [ADMIN] Postgesql and SSL
>> To: pgsql-admin@postgresql.org
>> Date: Saturday, 28 February, 2009, 10:18 PM
>> Hello,
>>
>>  I am trying to run PostgreSQL with SSL, so I compiled and
>> linked with
>> options:
>>
>> ./configure --prefix=/DB --with-openssl
>>
>> Configured and installed successfully.
>> In postgresql.conf I have option "ssl = on"
>> When starting Postgres I get error:
>> LOG:  SSL is not supported by this build
>> FATAL:  invalid value for parameter "ssl": 1
>> DEBUG:  proc_exit(1)
>> DEBUG:  shmem_exit(1)
>> DEBUG:  exit(1)
>>
>> Where is the problem? Is here versions which does not
>> support SSL, it
>> would be strange..
>>
>> Versions used:
>> PostgreSQL 8.3.4
>> OpenSSL 0.9.8j
>>
>>
>>
>> --
>> Lukas
>> UAB nSoft
>> http://www.nsoft.lt
>> Lukas at nsoft.lt
>> +370 655 10 655
>>
>>
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by
>> OpenProtect(http://www.openprotect.com), and is
>> believed to be clean.
>>
>>
>> --
>> Sent via pgsql-admin mailing list
>> (pgsql-admin@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-admin
>
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
> --
> This message has been scanned for viruses and
> dangerous content by OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>
>



--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.