Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2023

Debian/Ubuntu service provider improvements

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.4.3
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
      None
    • Template:

      Description

      Currently on Debian the debian service provider is selected, which uses standard SysV /etc/init/* for start/stop and update-rc.d to enable/disable services.

      The Debian CTTE has decided in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708#6734 that the default init implementation for Jessie (Debian 8.0) on Linux platforms is going to be systemd. At the same time at least sysvinit, upstart and openrc are going to be available for users to choose.

      This will also affect Ubuntu in the long run, since Marc Shuttleworth has announced Ubuntu switching to SystemD as well, which will most likely have a transition period too.

      The systemd supports most Debian packages being controlled by /etc/init.d/* (using redirection functions) it is definitely not the recommended way and will spectacularly fail for services that do not have a standard init script anymore.

      I don't have a good and tested solution for that. Hardcoding Debian 8.0 to systemd will also break things. I can think of two options:

      • auto-detect the running init system and use the appropriate provider
      • use /usr/bin/invoke-rc.d in the Debian provider for start/stop/reload/status

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              bschmidt Bernhard Schmidt
              QA Contact:
              Eric Thompson
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support