Closed chenein closed 6 months ago
Oops, I got confused for a moment, please ignore 9f1cce3d0e53209180eabbcd48878c1e989101e7, I just reverted it. The real fix is in 248fb833f9883b714c48cd3edac2b212cbcd565f.
I actually wanted to follow OpenBSD' httpd behaviour and open the log files inside the chroot; in this case the documentation was right and the code had a bug.
Thanks for the report!
I'm about to close this issues since 2.0.2 was released and includes this bugfix. Thanks!
Got gmid going today on my FBSD server with the chroot configuation. Wanted to use a text logfile. At first I created the path within the chroot but server couldn't open it. Realized it may be an exception to chroot, created in the main filesystem and it worked.
The documentation for the chroot option currently reads "All the paths in the configuration file are relative to the chroot directory, except for the cert, key and ocsp paths." Also the log access option says "The path is relative to the chroot."
My experience is that this is misleading, and a change to the documentation may be warranted. Alternatively, if the plan is to open the logfile within the chroot, this is not my experience.