diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-March/013156.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-March/013156.html | 81 |
1 files changed, 81 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/013156.html b/zarb-ml/mageia-dev/2012-March/013156.html new file mode 100644 index 000000000..fcc339153 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013156.html @@ -0,0 +1,81 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] lighttpd and others now require apache + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20lighttpd%20and%20others%20now%20require%20apache&In-Reply-To=%3C4F63018E.6050603%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="013145.html"> + <LINK REL="Next" HREF="013164.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] lighttpd and others now require apache</H1> + <B>Guillaume Rousse</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20lighttpd%20and%20others%20now%20require%20apache&In-Reply-To=%3C4F63018E.6050603%40gmail.com%3E" + TITLE="[Mageia-dev] lighttpd and others now require apache">guillomovitch at gmail.com + </A><BR> + <I>Fri Mar 16 10:02:06 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="013145.html">[Mageia-dev] lighttpd and others now require apache +</A></li> + <LI>Next message: <A HREF="013164.html">[Mageia-dev] lighttpd and others now require apache +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13156">[ date ]</a> + <a href="thread.html#13156">[ thread ]</a> + <a href="subject.html#13156">[ subject ]</a> + <a href="author.html#13156">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 16/03/2012 03:01, Anssi Hannula a écrit : +>><i> So I'd rather revert the change, and make lighttpd autonomous also. +</I>>><i> Unless someone can convince me there is an advantage having lighttpd +</I>>><i> executing as 'apache' :) +</I>><i> +</I>><i> The web applications policy has files being owned by 'apache' user, and +</I>><i> I don't see how that could work if lighttpd used a different user: +</I>><i> <A HREF="https://wiki.mageia.org/en/Web_applications_policy">https://wiki.mageia.org/en/Web_applications_policy</A> +</I>This policy was crafted with apache in mind only, not all available web +servers. And its explicitely refers to apache integration, not generic +webserver compatibility. For instance, the configuration file provided +is apache-specific. Even if we have compatible file permissions, and if +we asked packagers to also provide a default lighttpd configuration file +(slighly more work), that would still be mostly theorical compatibility +without actual testing from the packagers (many more work). + +So, rather than a potential compatibility, without documented limits, +should we rather not make clear than adapting our web applications +package to any other web server than apache is fully up to the end user ? + +-- +BOFH excuse #202: + +kernel panic: write-only-memory (/dev/wom0) capacity exceeded. +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="013145.html">[Mageia-dev] lighttpd and others now require apache +</A></li> + <LI>Next message: <A HREF="013164.html">[Mageia-dev] lighttpd and others now require apache +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13156">[ date ]</a> + <a href="thread.html#13156">[ thread ]</a> + <a href="subject.html#13156">[ subject ]</a> + <a href="author.html#13156">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |