We are doing a project for a large corporate client. The client wants us to run the website on their preferred provider's infrastructure. This provider, however, does not allow the use of php's syslog() and openlog() functions because of security reasons.
As far as we can tell all calls to syslog() and consequently also to openlog() can be removed because they are only used for debugging purposes. For now we replaced all calls to syslog() with calls to drupal's watchdog() function and commented out the call to openlog() (see patch in comment below).
In the end this is not the solution. The solution lies in includes/database.inc. Here a number of Exception classes are defined that should be used for exception handling in the oracle database driver. This way the exceptions take care of all logging. The sqlite database driver demonstrates that very nicely.
Would it be possible to add this to a next release.
| Comment | File | Size | Author |
|---|
Comments
Comment #1
Jan van Diepen commentedComment #1.0
Jan van Diepen commentedForgot to attach patch file. Added it in comment. Changed text to refer to comment.
Comment #2
bohartD7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
Everyone can apply the patches/suggestions above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.
Thanks!