Have you tried viewing it in a different browser? Read this from the KDE FAQ: Is there a way to change the timeout values in Konqueror ? Beginning with 2.2 beta series, you can change the timeout settings in the control panel under "Network->Preferences". If you are using the 2.1 series, however, you have to manipulate the config file manually to adjust these values to your liking. Here is the procedure for doing that: Open $KDEHOME/share/config/kioslaverc in your favorite editor, where $KDEHOME is your local kde config directory (usually ~/.kde/). Add the following entries without any HEADING, i.e outside of any [] block. Simply adding it to the top of the file will suffice. ReadTimeout=x // length of time to wait for arrival of requested data ResponseTimeout=x // length of time to wait for a response after sending a request ConnectTimeout=x // length of time to wait for response after attempting to connect ProxyConnectTimeout=x // same a above except it is used for proxy servers. where x is the value you need in seconds. To give you an idea, here are the default values: DEFAULT_READ_TIMEOUT 15 // 15 SECONDS DEFAULT_RESPONSE_TIMEOUT 60 // 1 MINUTE DEFAULT_CONNECT_TIMEOUT 20 // 20 SECONDS DEFAULT_PROXY_CONNECT_TIMEOUT 10 // 10 SECONDS Manually run the following command to update any running io-slaves: dcop konqueror KIO::Scheduler reparseConfiguration() "" If you are running older than version 2.1 of KDE, upgrade. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Josh Berkus" <josh@xxxxxxxxxxxx> To: <pgsql-php@xxxxxxxxxxxxxx> Sent: Friday, October 05, 2001 12:55 PM Subject: Re: [PHP] Help with timeouts > Papp, > > > So is there anything you forgot to mention ;) > > I mean everything works fine except this query or you couldn't test > > the page > > without the result. > > Nope. Just waitin' for the query. > > There's a couple of things that make us believe it's the browser: > > 1. The timeout message on Konqueror is a dialog box, not a web page. > 2. Sometimes (we think) the query returns in just under 60 seconds (it's > been clocked from the command line at 55) and it takes a few more > seconds for the server to generate the HTML. The browser still times > out. > > > Have you tried to optimize this query? > > Maybe post to this list and wait for some suggestions... > > It's a procedure, actually, with about 16 steps. It's likely that we'll > break it down into 3-4 sub procedures for "progress reporting" purposes. > This will slow down the process overall but prevent browser timeouts. > > -Josh > > > ______AGLIO DATABASE SOLUTIONS___________________________ > Josh Berkus > Complete information technology josh@xxxxxxxxxxxx > and data management solutions (415) 565-7293 > for law firms, small businesses fax 621-2533 > and non-profit organizations. San Francisco > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@xxxxxxxxxxxxxx >
