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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] minor systemd-related issues
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20minor%20systemd-related%20issues&In-Reply-To=%3C4F874F92.20903%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="014208.html">
<LINK REL="Next" HREF="014218.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] minor systemd-related issues</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20minor%20systemd-related%20issues&In-Reply-To=%3C4F874F92.20903%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] minor systemd-related issues">mageia at colin.guthr.ie
</A><BR>
<I>Thu Apr 12 23:56:34 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="014208.html">[Mageia-dev] minor systemd-related issues
</A></li>
<LI>Next message: <A HREF="014218.html">[Mageia-dev] minor systemd-related issues
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14212">[ date ]</a>
<a href="thread.html#14212">[ thread ]</a>
<a href="subject.html#14212">[ subject ]</a>
<a href="author.html#14212">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and David Walser at 12/04/12 21:25 did gyre and gimble:
><i> Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at ...</A>> writes:
</I>>>><i> httpd is running, but it is using the LSB init script instead of
</I>>>><i> systemd units. I believe Colin's intention was to have
</I>>>><i> apache-mpm-prefork install a symlink to httpd-prefork.service called
</I>>>><i> httpd.service, but this symlink does not exist.
</I>>><i>
</I>>><i> Are you sure? The %post script should certainly have done that....
</I>>><i>
</I>>><i> [colin <at> jimmy ~]$ rpm -q --scripts apache-mpm-prefork
</I>>><i> postinstall scriptlet (using /bin/sh):
</I>>><i> ln -s /lib/systemd/system/httpd-prefork.service
</I>>><i> /etc/systemd/system/httpd.service 2>/dev/null || :
</I>>><i>
</I>>><i> I guess the only possible explanation I can think of here is that
</I>>><i> somehow, apache-mpm-prefork was upgraded before systemd was installed!
</I>>><i> Perhaps we need to make sure system is installed early in the process?
</I>><i>
</I>><i> I am sure. The only symlink in /etc/systemd/system is default.target,
</I>><i> everything else there is directories. Is that the right place to put that
</I>><i> symlink anyway?
</I>
Yes, the /etc/.... tree is the right place for this as it's a symlink
that could get overwritten by another mpm should the user decide it's
the correct mpm for their setup. The generic httpd.service link serves
two purposes here: 1. is to allow users to still refer to "httpd"
service (i.e. the command "service httpd restart" will still work, and
likewise calling the sysvinit script directly will also still redirect
properly to systemctl) and 2. is to allow a smooth upgrade from mga1
such that the "enabled" state of the httpd service is properly migrated too.
><i> I hadn't thought of the possibility that systemd not being installed is the
</I>><i> problem, but I guess that's the only logical explanation (unless systemd somehow
</I>><i> swept that directory and deleted it for some reason). I guess maybe the mpm
</I>><i> packages just need Requires(pre): systemd-units
</I>
Maybe, but looking at deps, basesystem requires systemd which requires
the units. Perhaps on upgrade, basesystem was not upgraded early enough.
Or maybe rpm-helper was not installed early enough... dunno. I can't
help but feel it would be overkill to add it to the mpm packages as a
Requires(pre) - it feels like it's something we should just be able to
rely on. That said, it would certainly work!
Thinking about it, I reckon rpm-helper especially should be something
that is always installed first on a big upgrade. There could be multiple
files running e.g. %_post_service etc. in their post scripts but we
certainly want the latest rpm-helper for that.
Perhaps something to check out.
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="014208.html">[Mageia-dev] minor systemd-related issues
</A></li>
<LI>Next message: <A HREF="014218.html">[Mageia-dev] minor systemd-related issues
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14212">[ date ]</a>
<a href="thread.html#14212">[ thread ]</a>
<a href="subject.html#14212">[ subject ]</a>
<a href="author.html#14212">[ 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>
|
