Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OTOBO Daemon should handle changes in Kernel/Config.pm #44

Closed
bschmalhofer opened this issue May 25, 2020 · 3 comments
Closed

OTOBO Daemon should handle changes in Kernel/Config.pm #44

bschmalhofer opened this issue May 25, 2020 · 3 comments
Milestone

Comments

@bschmalhofer
Copy link
Contributor

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.

@bschmalhofer
Copy link
Contributor Author

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.

@bschmalhofer
Copy link
Contributor Author

This has been implemented. Closing as there are no complaints yet.

@bschmalhofer bschmalhofer added this to the OTOBO 10.0 milestone Jul 22, 2020
bschmalhofer added a commit that referenced this issue May 25, 2021
for RotherOSS/CodePolicy:#44
@bschmalhofer
Copy link
Contributor Author

Looks like there was a problem with the spelling in the branch name that contained the changes for this issue. The relevant commits ended up in #41 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant