Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 3, 2016 at 8:56 AM, Solomon Peachy <pizza@xxxxxxxxxxxx> wrote:
> On Wed, Aug 03, 2016 at 12:15:09AM -0400, Nico Kadel-Garcia wrote:
>> Those do get ported. I didn't mean to be confusing. "buildbot", the
>> Python based build tool, is unlikely to ever be ported. Not that it's
>> a very good tool, but it remains additionally unlikely to be ported
>> due to the extra burden of having to provide system admin provided
>> systemd integration.
>
> https://github.com/buildbot/buildbot/blob/master/master/contrib/systemd/buildbot.service
>
> This commit landed in January, 2014, and sits alongside an example
> sysvinit script.  Fedora's packages include neither, not even as
> exmples -- there's no provided init integration at all.

Interesting, and thank you for the pointer. It was not in the tag that
I last worked with.

> Incidently, I wouldn't consider buildbot an example of a "decades-old"
> daemon for which systemd adds nothing; indeed it's one of the most
> finiky and brittle tools I've ever used, and systemd's isolation,
> logging, and cleanup features are greatly beneficial when trying to
> figure out why buildbot has crapped out yet again.

Oh, dear lord, I agree it's horrible and does nothing that Jenkins or
even Hudson didn't master a decade ago. I'm having some difficulty
finding decades old standards that haven't either died, or have
finally gained systemd support. Much of the systemd support remains
outside the primary source repository for many daemons, including
httpd and OpenSSH and Subverison that I mentioned. Buildbot... has
surprised me by having enough suckers stuck using it to ever have
gotten systemd tools written for it.

One of the benefit of a sysvinit script that I've not personally made
clear is that it's easier to start it *from the console*, and activate
gdb or a graphical debugger around it the running binary. I've never
seen anyone get that working for systemd, and activating the daemons
in systemd typically requires administrative privileges. It's often
easier to activate a daemon with a raw init script, as a local user,
without adding the potentially fragile intricacies of running it as a
systemd daemon. If it fails once, you get one core file suitable for
debugging, and the daemon stays *dead* until manually restarted.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux