Confirmed with Natty (11.04), as well as with Oneiric with the 20110912 image. Since I assume everything else is running OK with the amavis-new/razor combination, I think this bug does belong to the "razor" package.
I think it's good policy to have razor running as a nonprivileged user. The consequence is that it will then be unable to create any files under /var/log/ since that's writable only by root.
I can think of two possible solutions:
1- The installation script should create /var/log/razor-agent.log as an empty file and make it writable by the user razor-agent runs as.
2- The config file /etc/razor/razor-agent.conf should point to a different location, one that's actually writable by the razor-agent user. Maybe /var/log/razor-agent/ which would also have to be created by the installation script.
1 can potentially be implemented as a packaging task, while 2 would require messing around with the config files and is potentially more involved but seems cleaner in my opinion.
Anyway, since I confirmed this both on Natty and Oneiric and potential solutions are described here, I'll set as Triaged, with importance: Low since the solutions I propose can be implemented by hand and constitute very easy workarounds. Still, I agree that this should eventually be fixed in the package itself.
Confirmed with Natty (11.04), as well as with Oneiric with the 20110912 image. Since I assume everything else is running OK with the amavis-new/razor combination, I think this bug does belong to the "razor" package.
I think it's good policy to have razor running as a nonprivileged user. The consequence is that it will then be unable to create any files under /var/log/ since that's writable only by root.
I can think of two possible solutions:
1- The installation script should create /var/log/ razor-agent. log as an empty file and make it writable by the user razor-agent runs as.
2- The config file /etc/razor/ razor-agent. conf should point to a different location, one that's actually writable by the razor-agent user. Maybe /var/log/ razor-agent/ which would also have to be created by the installation script.
1 can potentially be implemented as a packaging task, while 2 would require messing around with the config files and is potentially more involved but seems cleaner in my opinion.
Anyway, since I confirmed this both on Natty and Oneiric and potential solutions are described here, I'll set as Triaged, with importance: Low since the solutions I propose can be implemented by hand and constitute very easy workarounds. Still, I agree that this should eventually be fixed in the package itself.
Thanks for your report!
--- wiki.ubuntu. com/BugSquad
Ubuntu Bug Squad volunteer triager
http://