blob: dc44896786b678958a9ff7b916c5195d6323da5b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
<!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=%3C4F68B4C6.3060509%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013185.html">
<LINK REL="Next" HREF="013345.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=%3C4F68B4C6.3060509%40gmail.com%3E"
TITLE="[Mageia-dev] lighttpd and others now require apache">guillomovitch at gmail.com
</A><BR>
<I>Tue Mar 20 17:48:06 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013185.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013345.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13276">[ date ]</a>
<a href="thread.html#13276">[ thread ]</a>
<a href="subject.html#13276">[ subject ]</a>
<a href="author.html#13276">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 17/03/2012 03:22, Anssi Hannula a écrit :
><i> Hence I suggest a single user id to be used. (I'm fine with any other
</I>><i> solution which works as well)
</I>My main concern is the fuzziness of the current situation where we have
- one virtual package 'webserver' corresponding to four implementations
(apache, lightpd, nginx, cherooke)
- one common base (webserver-base) only used by the two first ones
- all our web applications packages using 'apache' as mandatory dependency
If the main concern is file ownership, I'd propose for the next release
to have each of these servers use a distinct uid, document root and
index page, but use a shared 'webserver' or 'www' gid, and ensure all of
those applications use group-based permission, instead of user-based.
I'd find this setup a bit clearer.
--
BOFH excuse #339:
manager in the cable duct
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013185.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013345.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13276">[ date ]</a>
<a href="thread.html#13276">[ thread ]</a>
<a href="subject.html#13276">[ subject ]</a>
<a href="author.html#13276">[ 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>
|