set_time_limit(3600 * 48); but process ever run only by three hours, how fix that?

[httpd_config.conf]

hi,

we need run socket.php by weeks... ("eternally") then we add the line

set_time_limit(3600 * 48);

but ever the process dead EXACTLY after of 3 hours

how we can run process by minimum 1 week ?

thanks



[root@pepsi ~]# php -v
PHP 8.0.30 (cli) (built: May 13 2025 19:33:03) ( NTS gcc x86_64 )
Copyright (c) The PHP Group
Zend Engine v4.0.30, Copyright (c) Zend Technologies
[root@pepsi ~]#


[root@pepsi ~]# more /etc/redhat-release
AlmaLinux release 9.6 (Sage Margay)
[root@pepsi ~]#


[root@pepsi ~]# /usr/local/lsws/bin/lshttpd -v
LiteSpeed/1.8.4 Open (BUILD built: Mon Sep 29 17:17:57 UTC 2025)
module versions:
lsquic 4.3.1
modgzip 1.1
cache 1.66
mod_security 1.4 (with libmodsecurity v3.0.14)
[root@pepsi ~]#


[root@pepsi ~]# echo -n 'CyberPanel versión ';head -1 /usr/local/CyberCP/version.txt
CyberPanel versión 2.4
[root@pepsi ~]#

 

[LiteCache]

LiteSpeed Enterprise (LSWS) uses LSAPI_MAX_PROCESS_TIME Environment Variable
https://docs.litespeedtech.com/lsws...t-lsapi_max_process_time-environment-variable

But don't know if OLS supports it. If not, run the script in console.

 

[httpd_config.conf]

thanks,

console BREAK the program

 

[neikoloves]

LiteSpeed Enterprise (LSWS) uses LSAPI_MAX_PROCESS_TIME Environment Variable
https://docs.litespeedtech.com/lsws...t-lsapi_max_process_time-environment-variable

But don't know if OLS supports it. If not, run the script in console.

I'm investigating LiteCache's capabilities for high-complexity WordPress and WooCommerce site. My current observations suggest existing caching solutions struggle with:

• Intricate plugin interactions
• Dynamic content generation
• Complex e-commerce configurations

Could you provide technical details on how LiteCache addresses these advanced site requirements?

I'm also experiencing access challenges through CloudFlare that are preventing a thorough evaluation of your site.

Your insights would be appreciated, I know this is not the best thread, but it's the most recently active I could find for you. Thank you.

 

[LiteCache]

@neikoloves

Before we talk about your post, we need to clarify what you are referring to, because the topic of this thread is something completely different.