On Tue, Mar 6, 2012 at 4:45 PM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
2012/3/6 Richard Shaw <hobbes1069(a)gmail.com>:
> On Tue, Mar 6, 2012 at 4:39 PM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
>> 2012/3/5 Richard Shaw <hobbes1069(a)gmail.com>:
>>> I know the policy is to not change from sysv init to systemd within a
>>> release but I was thinking that akmods is pretty low risk. The main
>>> reason being you're not likely to want to install it and then disable
>>> it. Presumably, if you install it you want it to run.
>>> I was only thinking about this for F16 since F15 will be EOL soon enough.
>>> Comment? Concerns?
>> Which bug does that backport will solve ?
ok so none.
I wonder sometimes if it's your goal to be unhelpful in as few words
as possible. Do you go out of your way to be this acidic or does it
just come naturally? It's not my intention to start an argument here,
but ignoring your comments is becoming increasingly difficult. If you
want to run everything by yourself then just tell me so I can get all
of my packages assigned to you. If not, I suggest you at least try to
take the path of a teacher instead of looking down on everyone who
doesn't know as much as you.
Since I'm not getting paid for this, I'm definitely not getting paid
enough to put up with this shit.
Back to the subject at hand, the bug is that for some reason the LSB
entry in the SysV file says there should be a PID file but I can not
find where, if at all, in the akmods script it's created. Sure I could
just remove the PID entry but since this is F16 we're talking about I
thought it would be nice to use a native systemd service file since
I'm not sure what issues the SysV compatibility can cause in this type
of service, which is not a daemon.