[Bug 396632] Re: lighttpd init file should not chown or chmod on status check
** Changed in: lighttpd (Ubuntu) Status: Incomplete => Triaged ** Changed in: lighttpd (Ubuntu) Importance: Undecided => Low -- lighttpd init file should not chown or chmod on status check https://bugs.launchpad.net/bugs/396632 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 396632] Re: lighttpd init file should not chown or chmod on status check
Sorry, I meant bug 109559--I had the wrong one in my clipboard. -- lighttpd init file should not chown or chmod on status check https://bugs.launchpad.net/bugs/396632 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 396632] Re: lighttpd init file should not chown or chmod on status check
I believe this is related to bug 424991 in that `/etc/init.d/lighttpd` assumes directory locations and 109559 and permissions when this should be pulled from a config file like `/etc/default/lighttpd` or something. I'm not familiar enough with with bash scripting to know what to do to fix this, otherwise I would write a patch. Could someone else please either confirm or deny that this is a bug? -- lighttpd init file should not chown or chmod on status check https://bugs.launchpad.net/bugs/396632 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 396632] Re: lighttpd init file should not chown or chmod on status check
I believe that is the offending code. Now that I think about it I should have titled this bug differently. The issue I saw was `/etc/init.d/lighttpd status` cannot be run as a non-root user. When I looked into why it couldn't be run, I saw that quoted code. Plus, shouldn't the user and group be pulled from a config file? Please let me know if I am missing something. Thanks. -- lighttpd init file should not chown or chmod on status check https://bugs.launchpad.net/bugs/396632 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 396632] Re: lighttpd init file should not chown or chmod on status check
I cannot confirm this. Are you referring to the following snippet? # be sure there is a /var/run/lighttpd, even with tmpfs mkdir -p /var/run/lighttpd > /dev/null 2> /dev/null chown www-data:www-data /var/run/lighttpd chmod 0750 /var/run/lighttpd ** Changed in: lighttpd (Ubuntu) Status: New => Incomplete -- lighttpd init file should not chown or chmod on status check https://bugs.launchpad.net/bugs/396632 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
