Troubleshooting and FAQs

This page deals with frequently asked questions related to the Zentitle2Core library.

1. Enabling Logging

Issue: How can I turn on logging in the Zentitle2Core library?

To enable logging in the Zentitle2Core library, you need to call the function before using any other Zentitle Core Client library functions.

/**
 * \brief Initializes the logger.
 * This function must be called before any other Zentitle Core Client library functions.
 * 
 * \param pathToLogFile - (Optional) Specifies the path to the log file.
 *                       If not specified, the log file will be created in the current working directory.
 *                       The file name will be in the format: zentitle2core_YYYYMMDD_HHMMSS.log
 */
ZENTITLE_CORE_LIB_EXPORT void enableLogging(char* pathToLogFile = nullptr);

You can optionally specify the pathToLogFile parameter to set the path to the log file. If not specified, the log file will be created in the current working directory with a default file name.

2. User Rights in MacOS and Linux

Issue: What user rights issues might occur when using dynamic loading libraries in MacOS and Linux?

Users may encounter user rights issues when attempting to load or access shared libraries while using dynamic loading libraries in MacOS and Linux. Here are some common scenarios and how to deal with them:

• Permission Denied: It's possible that you may come across a "Permission Denied" error while trying to load a shared library. This can occur if the application user doesn't have the required permissions to access the library file.

  Solution: Ensure the application user has read and execute permissions for the directory where the shared library is located. You may need to modify permissions using the chmod command.

• Library Not Found: The application may fail to locate the shared library, resulting in a "Library Not Found" error.

  Solution: Make sure that the library is located in one of the standard library paths or add the library path to the LD_LIBRARY_PATH (Linux) or DYLD_LIBRARY_PATH (MacOS) environment variable.

• Library Version Mismatch: Incompatibility between the expected and available library versions can cause issues.

  Solution: Make sure to use the correct library version that matches your application's requirements. If needed, update or install the library.

• Running as Root: Running an application with elevated privileges can cause security and compatibility issues.

  Solution: Avoid using applications with unnecessary elevated privileges. Instead, use appropriate user accounts with the required permissions.

By addressing these user rights and permission issues, you can ensure smooth operation when using dynamic loading libraries in MacOS and Linux.