Fedora seems to fix this by setting a hard coded umask into the source
code. Is this an approach we want to take?

It looks as if ntop only insists on creating global writable logs if the
option -d (--daemon) is used. Runnong non-daemonized it obeys umask
settings just fine.

I experienced the exact same behavior while downloading the latest
version from SVN.

@Jamie: While you were in contact with upstream, did they give you a
ticket number for this issue? I can't seem to find any in their Trac.

-- 
access.log is owned by root and has write permissions to anyone
https://bugs.launchpad.net/bugs/325393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to