Log file permissions
hvendelbo.dev at googlemail.com
Sun Jun 1 02:12:49 MSD 2008
Hmm, seems I have gotten a bit further. If I create the log files
myself and make them group writable with root:nobody, it doesn't write
an error. It still terminates the nginx process though, I wonder if
that is launchd getting confused by the master forking mechanism.
On Sat, May 31, 2008 at 10:55 PM, Henrik Vendelbo
<hvendelbo.dev at googlemail.com> wrote:
> I have tried with containing directory chown root:nobody and
> nobody:nobody, I have even tried giving everyone write access with
> chmod. Makes no difference.
> It's odd.
> On Fri, May 30, 2008 at 11:37 AM, Jeffrey 'jf' Lim <jfs.world at gmail.com> wrote:
>> On Fri, May 30, 2008 at 6:37 PM, Jeffrey 'jf' Lim <jfs.world at gmail.com>
>>> On Fri, May 30, 2008 at 6:29 PM, Henrik Vendelbo
>>> <hvendelbo.dev at googlemail.com> wrote:
>>>> I am quite stuck trying to set up access/error logging for nginx.
>>>> $ ls -al /var/log/testin2.local/
>>>> total 0
>>>> drwxrwxr-x 3 root nobody 102 30 May 00:17 .
>>>> drwxr-xr-x 85 root wheel 2890 30 May 00:00 ..
>>>> -rwxrwx--- 1 root nobody 5496 30 May 00:21 www.access.log
>>>> I run nginx as nobody:nobody, and group nobody should have write
>>>> access to the log file, even so it fails with this message:
>>> does anybody have write permissions to the containing directly? or does
>>> nobody have it?
>> containing directory, sorry.
>> In the meantime, here is your PSA:
>> "It's so hard to write a graphics driver that open-sourcing it would not
>> -- Andrew Fear, Software Product Manager, NVIDIA Corporation
More information about the nginx