Warning: pg_connect() unable to connect to PostgreSQL server: Sorry, too many clients already in
/home/sdlweb/libsdl.org/web/include/login.inc.php on line 25
Could not connect to the database !
ugh…
-LIM-
In message <41EA48B2.2000507 at jcatki.no-ip.org>
Jonathan Atkins wrote:
Warning: pg_connect() unable to connect to PostgreSQL server: Sorry, too many clients already in
/home/sdlweb/libsdl.org/web/include/login.inc.php on line 25
Could not connect to the database !ugh…
I’m getting the same thing here - looks like the database server has fallen
over 
Damn shame - I wanted to take a look at the list archives earlier - fat
chance.
Who’s responsible for maintaining LibSDL.org anyway?
Later.–
Phil. | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB,
philpem at philpem.me.uk | ViewFinder, 10BaseT Ethernet, 2-slice,
http://www.philpem.me.uk/ | 48xCD, ARCINv6c IDE, SCSI
… Happiness is finding special characters
Hello !
Damn shame - I wanted to take a look at the list archives earlier - fat
chance.
The Mailing List archives are still online,
http://www.libsdl.org/mailman/listinfo/
CU
In message <41EC455D.9010905 at jcatki.no-ip.org>
Jonathan Atkins wrote:
releases and changelogs can still be reached at http://www.libsdl.org/release/
And the wiki is still up at http://www.libsdl.org/cgi/docwiki.cgi/.
Now all we need is for someone to fix the main webserver and we’re sorted 
Later.–
Phil. | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB,
philpem at philpem.me.uk | ViewFinder, 10BaseT Ethernet, 2-slice,
http://www.philpem.me.uk/ | 48xCD, ARCINv6c IDE, SCSI
… We do what we can but it’s never enough.
Jonathan Atkins <jcatki at jcatki.no-ip.org> wrote:releases and changelogs can still be reached at http://www.libsdl.org/release/
And the wiki is still up at http://www.libsdl.org/cgi/docwiki.cgi/.
Now all we need is for someone to fix the main webserver and we’re sorted
I’m somewhat working on it… I can’t fix the problem with the
database (I don’t know what is the problem anyway), but I’ll commit an
updated version of the homepage on the CVS in an hour or so. It’ll
handle the database problem more gracefully.
We could still have to wait for Sam to check it out from the CVS to
the webserver directory…
All the database-driven features will still be unavailable though…
-Gaetan.On Tue, 18 Jan 2005 00:24:04 GMT, Philip Pemberton wrote: