[phpa] Re: problem with p4

Hi,

Thanks for the comments.  Most likely I'll do a fix soon. If feasible, you
could work around it by setting domains with long names in the virtual host
sections as before. All 3 registration mechanisms can be used together.

There's a warning message that people may get about the cache being locked
by an unknown pid, and that isn't really a problem but annoying, so I'll
address that too.  If I can, then I'll try to accomodate any other necessary
fixes into the next release too. 

nick


> 
>> It was much longer but I reduced it for
>> testing purposes and evidently it wasn't
>> increased again.  It will be increased.
> 
> Glad its not just be that does that kind of things :-)
> 
> I just got the same problem here and Monte just beat me to reporting
> it. That was on my internal server (longhostname.penguin); so only one
> broke, but if I try them live most will probably fail. Is the fix going
> to be anytime soon, and/or does the old method work in the meantime?
> 
> [PS: I've been following the list for a while but 1.2p4 is my first
> installation now that I've upgraded PHP on my server. So far I'm very
> impressed with phpa - I've had some odd problems and each one has so
> far turned out to be related the PHP upgrade and none apart from this
> one due to phpa. Keep up the good work!]
> 
> Mark Rogers, Quarella Ltd
> 
> ------------------------------------------------------------------------
>   www.php-accelerator.co.uk           Home of the free PHP Accelerator
> 
> To post, send email to phpa@xxxxxxxxxxxxx
> To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject
> unsubscribe


------------------------------------------------------------------------
  www.php-accelerator.co.uk           Home of the free PHP Accelerator

To post, send email to phpa@xxxxxxxxxxxxx
To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe

Other related posts: