Software: Apache/2.4.41 (Ubuntu). PHP/8.0.30 

uname -a: Linux apirnd 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64 

uid=33(www-data) gid=33(www-data) groups=33(www-data) 

Safe-mode: OFF (not secure)

/usr/share/doc/autogen/autogen.html/   drwxr-xr-x
Free 13.4 GB of 57.97 GB (23.12%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Self remove    Logout    

Viewing file:     Multi_002dThreading.html (3.58 KB)      -rw-r--r--

7.7 Multi-Threading

AutoOpts was designed to configure a program for running. This generally happens before much real work has been started. Consequently, it is expected to be run before multi-threaded applications have started multiple threads. However, this is not always the case. Some applications may need to reset and reload their running configuration, and some may use SET_OPT_xxx() macros during processing. If you need to dynamically change your option configuration in your multi-threaded application, it is your responsibility to prevent all threads from accessing the option configuration state, except the one altering the configuration.

The various accessor macros (HAVE_OPT(), etc.) do not modify state and are safe to use in a multi-threaded application. It is safe as long as no other thread is concurrently modifying state, of course.