On Mon, Jul 8, 2013 at 9:27 PM, Olaf van der Spek <olafvds...@gmail.com> wrote: > On Sun, Jul 7, 2013 at 12:49 AM, Christophe-Marie Duquesne <c...@chmd.fr> > wrote: >> TL;DR It would be nice if the init script was loading the user/group >> of lighttpd from a unique config file > > That'd only 'solve' a small part of the problem, wouldn't it?
Well, provided the config file is doing the same thing, that would enable the user to modify the user/group in only one place. Apache does this through environment variables, and the file /etc/apache2/envvars, I thought it would be nice to have a similar trick for lighttpd... Or at least, to have all the places assuming www-data documented as a comment just above the relevant lines of the default /etc/lighttpd/lighttpd.conf. > What's the reason for running Lighttpd as another user? Ahem... No real answer, apart from "because lighttpd theoretically allows me to do so". The option is there in the config file, so I would expect to be able to use it. To complement this non-answer, I'll say I find it handy to have lighttpd run as a "real" user that has a directory in /home. I can run other programs as this user, and modify files without having to care about umasks or default owner. I also like to have lighttpd being able to modify those files. But I guess this is a matter of taste. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org