Hi Jeff, >>>compare your code with apr-util/test/testdbm.c and see why testdbm.c >>>works and yours doesn't did that, and the testdbm works fine; so there's not the problem; also the dbm open is the same as with my code.
> the dbm support, and in fact apr/apr-util as a whole, knows nothing of > Apache or its log directories... if you want to create a file in > Apache's log directories you'll need to find that directory and specify > it on the open that's what I do already; but what I meant was why Apache _can_ create files in the log dir while my module cant with the dbm open without touching the files first and setting permission by hand? I tested some further and found that my code works and creates the sdbm files if I specify f.e. /var/tmp; so it really is a permission issue. My Apache2 runs as 'User nobody' and 'Group nogroup'; I've compiled and installed Apache2 as root; the log dir and all other dirs below /usr/local/apache2 are 755; so I made the log dir 777 and now the sdbm files are created! So now my question is: how does Apache handle the log files?? They are 644 and root/root, while my sdbm files are now 644 nobody/nogroup; and is it possible to fix my issue if I create the sdbm files already during module initialisaton?? Are they then created by root, and if so can the module later access them?? And how does Apache log to the root/root files when running as nobody/nogroup?? What is the recommend way here? My apologies for all these stupid permission questions! thanks for your help! Guenter.
