Bug 64814 - Add lock database path in the log message mod_dav
Summary: Add lock database path in the log message mod_dav
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dav (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: PatchAvailable
Depends on:
Blocks:
 
Reported: 2020-10-15 03:42 UTC by Tianyi Shan
Modified: 2020-10-15 18:00 UTC (History)
1 user (show)


Attachments
patch diff (1.40 KB, patch)
2020-10-15 03:42 UTC, Tianyi Shan 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tianyi Shan 2020-10-15 03:42:45 UTC 
Created attachment 37502 [details]
patch diff

Add database path in the log messages of dav_generic_really_open_lockdb and dav_fs_really_open_lockdb to show the lock database's path. The previous log message logs "Could not open the lock database”, but don’t have the detailed path of the lock database. Sysadmins may need to check the FS permissions for the path to resolve the problem. [1]

[1] https://stackoverflow.com/questions/7619658/could-not-open-property-database.