Steffan Hoeke <[EMAIL PROTECTED]> wrote:

>On Thu, Jun 29, 2000 at 12:21:33PM -0400, Dave Sill wrote:
>> Steffan Hoeke <[EMAIL PROTECTED]> wrote:
>> 
>> >On Thu, Jun 29, 2000 at 01:55:14AM +0200, clemensF wrote:
>> >> > Steffan Hoeke:
>> >> 
>> >> > "Ok, the /var/log/qmail permissions weren't the problem
>> >> > /var/qmail/supervise and all in it needed to be owned by qmaill as well ;)"
>> >> 
>> >> why that?
>> >No other reason than : Before the permission change qmail start would
>> >freak out with unable to change to current directory.  When i changed
>> >the permissions on /var/qmail/supervise and it's subs to qmaill.qmail
>> >it worked like a charm.
>> 
>> The real reason is that multilog runs as user qmaill.
>> 
>> >I know it's not a scientific approach, but i couldn't find anything
>> >in lwq about the proper permissions (Dave, if you're reading this
>> >;-))
>> 
>> It's in there:
>> 
>>   Then set up the log directories:
>> 
>>     mkdir -p /var/log/qmail/smtpd
>>     chown qmaill /var/log/qmail /var/log/qmail/smtpd
>
>Nope, this talks about the /var/log/qmail subtree.
>I'm talking about the /var/qmail/supervise subtree ;-)

Sorry, I read that too fast. You're right: LWQ doesn't set the owner
for the supervise directories because everything that accesses them
runs as root.

I can't explain the errors you saw...

-Dave

Reply via email to