From: Gary V <mr8...@gm...> - 2010-10-31 03:47:02
|
On 10/30/10, Mark Martinec wrote: > For the archive: > >> I can repro this on two out of two Debian lenny machines so far. I did >> not change any of the settings mentioned in prior posts. This happens >> without making any config file changes whatsoever. Here are more >> details on the two machines: > > It was a permission problem on a config file. A warm reload implies > that the new daemon process inherits the UID under which its parent run, > so it cannot read files accessible only to root - and neither can it > log the problem unfortunately, as it has no controlling terminal > not is it able to read the logging configuration settings. > > Mark > Indeed, changing my amavisd.conf from root:root 0640 to root:amavis 0640 allowed me to keep prying eyes from amavisd.conf and allowed 'amavisd reload' to function as designed in my various setups. I understand that repurposing 'reload' is the only logical choice for the command, but I imagine there are a lot of people who place the command in scripts (amavisd reload after sa-update for example) that may encounter the same issue I had. Like me, people don't always read the release notes, or when they do, they tend to skim through them looking for salient points and don't immediately recognize the implications of a change of this nature. Kind of like what dogs hear when humans speak to them: blah blah blah blah Lassie blah blah blah -- Gary V |