3.16.x on i686

[Adam Williamson]

On Tue, 2014-06-24 at 22:50 -0500, Bruno Wolff III wrote:
> On Tue, Jun 24, 2014 at 19:22:05 -0700,
>   Adam Williamson <awilliam at redhat.com> wrote:
> >
> >The most obvious thing is whether you have a SXXservice symlink
> >in /etc/rc*.d; that constitutes the service being 'enabled' so far as
> >SysV is concerned, and so in that case it seems correct for systemd to
> >enable the runtime-generated systemd service. But there may be other
> >reasons why this might happen, I think we'd best look at them case by
> >case.
> 
> I filed a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1112908) for 
> plague. Plague has both a systemd entry and an init.d file (but not 
> files for any run levels) for the plague-server service. That seems odd, 
> but I don't know if that is the cause of the problem.

So I think I have a handle on what's causing the bug of sysv services
starting when they're not supposed to - turns out to be (I think) a
fairly subtle bug in the sysv-generator code, if I'm right, then I'm
proud of myself for figuring it out :P See
https://bugzilla.redhat.com/show_bug.cgi?id=1112908#c9 . I'm currently
running a systemd scratch build which I hope is going to fix the
problem:

http://koji.fedoraproject.org/koji/taskinfo?taskID=7076318

assuming it builds successfully (AdamW Patching C: Take Cover!), if you
could test with that it'd be good.

sysv-generator actually landed in systemd-214 (not 209 as I'd thought),
so it makes sense that we're only just now seeing this bug crop up.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net