Configuration problem, razor is unable to log
Bug #848111 reported by
Geir Helland
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| razor (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When used with amavisd-new, razor runs as amavis:amavis, and has no write permisison for the configured log file "/var/log/
Not sure if this should be logged as a bug with amavisd-new or razor.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: razor 1:2.85-3
ProcVersionSign
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Mon Sep 12 19:35:41 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
LANGUAGE=nb_NO:en
LANG=nb_NO.UTF-8
SHELL=/bin/bash
SourcePackage: razor
UpgradeStatus: No upgrade log present (probably fresh install)
Revision history for this message
| Geir Helland (1aunchpad-nut) wrote | #1 |
Revision history for this message
| Daniel Manrique (roadmr) wrote | #2 |
| Changed in razor (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
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/
2- The config file /etc/razor/
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!
---
Ubuntu Bug Squad volunteer triager
http://