Scenario: nginx + PHP-FPM / FastCGI.
The final step of the deployment is updating a symlink to point to the
new version.
For N <= realpath_cache_ttl seconds after the deployment, some
filesystem operations fail because of outdated realpath cache entries.
Is there a way to signal the PHP-FP
Hi Remi, Pierre
2015-05-29 13:06 GMT+02:00 Remi Collet :
> Isn't a bit strange to drop this feature without discussion / RFC ?
>
> Especially when we keep mcrypt which also rely on a dead upstream, and
> which is much more problematic for security (crypto)
Sorry for the late late reply! First of
On 19 June 2015 at 13:43, Sebastian Bergmann wrote:
> Scenario: nginx + PHP-FPM / FastCGI.
>
> The final step of the deployment is updating a symlink to point to the
> new version.
>
> For N <= realpath_cache_ttl seconds after the deployment, some
> filesystem operations fail because of outd
On 06/19/2015 08:43 AM, Sebastian Bergmann wrote:
> Scenario: nginx + PHP-FPM / FastCGI.
>
> The final step of the deployment is updating a symlink to point to the
> new version.
>
> For N <= realpath_cache_ttl seconds after the deployment, some
> filesystem operations fail because of outdat
Alexandre (buhlerax) and I are going to rewrite PHP-GTK from scratch. In order
for me to do my part, I will need to be able to access the Git repository. I am
currently active in the php-gtk-dev mailing list.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:
