You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Understanding is that SecureMode = 0 indicates that OTOBO is being configured. In this situation running the Daemon might be problematic. How about adding a check for SecureMode that exits the Daemon when SecureMode = 0?
Alternatively Monitor Kernel/Config.pm and Reload it when it is changed. This could be done with Module::Refresh, or Module::Reload, or with Linux::Inotify2.
The text was updated successfully, but these errors were encountered:
The consensus is that Daemon.pl should watch Changes to ZZZAuto.pm and stop when it sees SecureMode = 0. The Cronjobs can still try to restart the Daemon every 5 Minutes.
My Understanding is that SecureMode = 0 indicates that OTOBO is being configured. In this situation running the Daemon might be problematic. How about adding a check for SecureMode that exits the Daemon when SecureMode = 0?
Alternatively Monitor Kernel/Config.pm and Reload it when it is changed. This could be done with Module::Refresh, or Module::Reload, or with Linux::Inotify2.
The text was updated successfully, but these errors were encountered: