| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su> |
| Cc: | "Michael Fuhr" <mike(at)fuhr(dot)org>, <pgsql-general(at)postgresql(dot)org>, <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] List archives search function broken |
| Date: | 2004-12-05 12:06:07 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE5621A@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-www |
> John,
>
> you could always rely on your script where you check if db
> handler is alive and if not then show gentle error message
> with link to www.pgsql.ru
I never check if dbhandler is alive in the frontend....
This was the backend OS that shut down, which also hosts the filesystems
for the scripts.... So that would have had the same result.
The 503 is hardcoded btw, tho it does have a method of displaying a
file. But that would be globally for all hosts, not just
search.postgresql.org
Frontend is pound reverse proxy running on the gateway.
The actual search is a backend running vmware
http://search.postgresql.org/phpsysinfo/
... John
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2004-12-05 16:11:06 | Re: Preview of Fourth PostgreSQL RFD. |
| Previous Message | Oleg Bartunov | 2004-12-05 11:53:33 | Re: [GENERAL] List archives search function broken |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2004-12-05 21:45:10 | New website mirroring |
| Previous Message | Oleg Bartunov | 2004-12-05 11:53:33 | Re: [GENERAL] List archives search function broken |