[pca] new --threads config

[Greg Matthews]

Martin Paul wrote:
> Greg Matthews wrote:
>> I dont think this config option works when pca is configured as a cgi 
>> proxy. Perhaps the docs could be updated to reflect this?
> 
> It doesn't make sense to use threads on a proxy, but it should do no 
> harm either.
> 
> I'm just investigating a problem with the threads option in general, 
> though, making pca (or the proxy) fail. Can you show me the 
> configuration file used for the proxy? It would be also interesting to 
> see how the proxy fails - an error message should be in apache's (the 
> web servers) error log file.
> 
> The workaround is of course to get rid of the threads setting for now. 
> When using pca with a local caching proxy, threads support really 
> doesn't make much sense.

yup, ok. I thought it might be clever enough to parellise the download 
from sunsolve... I have it disabled now anyway to get it working. My 
proxy config looks like this:

xrefdir=/local/spool/pca
patchdir=/local/spool/pca
user=<my sunsolve user name>
passwd=<my sunsolve passwd>
dltries=5
#threads=2

If I uncomment the threads directive, the apache error log throws this:

[Thu May 08 15:27:02 2008] [error] [client a.b.c.d] Undefined subroutine 
&main::share called at /var/www/cgi-bin/pca-proxy.cgi line 215.
[Thu May 08 15:27:02 2008] [error] [client a.b.c.d] Premature end of 
script headers: pca-proxy.cgi

GREG

> 
> Martin.
> 
> 


-- 
Greg Matthews           01491 692445
Head of UNIX/Linux, iTSS Wallingford

-- 
This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.