Zbigniew Szalbot wrote: > Hello, > > >> Simply open up permissions until it works. You used 770 (rwxrwx---) >> somewhere (was it /var/db/dspam maybe) and that is a bit odd for a >> directory, try 755 (rwxr-xr-x) instead, and so on. What's the permission >> for example on /var/db? /L > Ok. I chmod -R 755 /var/db/dspam
Good. > Right now as a www user I can access all data down until zbyszek.log file. That sounds like an improvement:) > When I open the GUI, I am still unable to see stats nor to save my > preferences. When I try to save the preferences, I get: > > An Error Has Occured > The following error occured while trying to process your request: > Unable to write preferences: No such file or directory > > There really isn't any prefs file in /var/db/dspam/data/domain/user/ but I > guess it should be created on the fly? That's what the GUI is trying to do. > So I tried running as a user www and: > > $ touch /var/db/dspam/data/szalbot.homedns.org/zbyszek/test.log > > $ ls -l /var/db/dspam/data/szalbot.homedns.org/zbyszek/ > -rw-r--r-- 1 www mailnull 0 Feb 1 20:35 test.log > -rwxr-xr-x 1 www mailnull 55934 Feb 1 20:33 zbyszek.log > > One thing I notice is that the file test.log created by user www has > different (more limited) permissions. Is that OK? Yes, it is. (it's actually zbyszek.log that is a bit off:) > Just to explain, I am only a few months old with regards to UNIX knowlegde > in general and am quite lost with all these permissions, etc. :) Trying to > learn but there is so much to acquire. So thank you for being patient with > me! No worries. Nevertheless, problem isn't solved yet: so what you're saying is that you can do whatever needs to be done at the command prompt as user www but not through the web GUI? There might be a need to restart the webserver, I don't know how much of the permissions and whatnot that gets cache'd. Restart and try again. Failing that, try to create the default.prefs file manually (you can copy it from the global one) and make sure you set the right owner and permissions. Restart the webserver and try again. /L
