[solved] systemctl package as an alternative to systemd?

Forum Forums New users New Users and General Questions [solved] systemctl package as an alternative to systemd?

  • This topic has 4 replies, 3 voices, and was last updated Aug 3-10:54 pm by olsztyn.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #86698
    Member
    stevesr0

      I have found several threads on this forum that say that “systemctl” is linked to systemd. For example, see Xecure’s post #45237.

      However, the systemctl package in the Debian unstable repository is described as a “daemonless” systemctl command to manage services without systemd. It’s source package is named docker-systemctl-replacement.

      It is a script whose only dependency is “any” python3.

      To me this suggests that it is an alternative to the systemctl that is part of systemd. And possibly not associated with the concerns that systemd carries for users who wish to avoid it.

      Why I care?

      I am running antiX Sid without systemd, using elogind and libelogind0 as substitutes. I am enjoying Pipewire and would like to use it with seatd instead. I have seen various schemes to run Pipewire on other nonsystemd distros.

      I found one site (https://github.com/pipewire-debian) that suggests that systemctl can be used to enable Pipewire without systemd. In it is the following:

      “Mx Linux or init system
      (Anyone using systemd ignore this subsection).

      For WirePlumber (Recommended)

      systemctl –user –now enable wireplumber.service”

      (end of quotation.)

      So I am wondering if anyone has experience with this (nonsystemd?) systemctl package.

      (Whether it will allow me to run Pipewire without elogind and libelogind0 is another story. I plan to query the github person about that.)

      Thanks in advance for comments.

      stevesr0

      • This topic was modified 9 months, 1 week ago by stevesr0.
      • This topic was modified 9 months, 1 week ago by stevesr0.
      • This topic was modified 9 months, 1 week ago by christophe. Reason: marked solved
      #86754
      Anonymous
        Helpful
        Up
        0
        ::

        I no longer run antiX with sid.

        Here under antiX-21_x64-base I have simulated some commands that prove that this systemctl package is readily installable and is not a dependency on systemd.

        inxi -Sxxx
        System:
          Host: antix21 Kernel: 5.10.104-antix.1-amd64-smp arch: x86_64 bits: 64
            compiler: gcc v: 10.2.1 Desktop: Fluxbox v: 1.3.7 vt: 7 dm: slimski
            v: 1.5.0 Distro: antiX-21_x64-base Grup Yorum 31 October 2021
            base: Debian GNU/Linux 11 (bullseye)
        
        apt policy systemctl
        systemctl:
          Installiert:           (keine)
          Installationskandidat: 1.4.4181-1.1
          Versionstabelle:
             1.4.4181-1.1 500
                500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
                500 http://ftp.de.debian.org/debian bullseye/main i386 Packages
        
        apt show systemctl
        Package: systemctl
        Version: 1.4.4181-1.1
        Priority: optional
        Section: admin
        Source: docker-systemctl-replacement
        Maintainer: Dmitry Smirnov <onlyjob@debian.org>
        Installed-Size: 279 kB
        Depends: python3:any
        Recommends: procps
        Suggests: tini | dumb-init
        Conflicts: systemd
        Homepage: https://github.com/gdraheim/docker-systemctl-replacement
        Download-Size: 79,8 kB
        APT-Sources: http://ftp.de.debian.org/debian bullseye/main amd64 Packages
        Description: daemonless "systemctl" command to manage services without systemd
         "systemctl" is a replacement command to control system daemons without
         systemd. "systemctl" is useful in application containers where systemd is
         not available to start/stop services.
         .
         This script can also be run as init of an application container (i.e. the
         main "CMD" on PID 1) where it will automatically bring up all enabled
         services in the "multi-user.target" and where it will reap all zombies
         from background processes in the container. When stopping such a container
         it will also bring down all configured services correctly before exit.
        
        apt rdepends --installed systemctl
        systemctl
        Reverse Depends:
        
        aptitude why-not systemctl
        Not currently installed
        The candidate version 1.4.4181-1.1 has priority optional
        No dependencies require to remove systemctl
        
        sudo apt install systemctl -s
        Paketlisten werden gelesen… Fertig
        Abhängigkeitsbaum wird aufgebaut… Fertig
        Statusinformationen werden eingelesen… Fertig
        Vorgeschlagene Pakete:
          tini | dumb-init
        Die folgenden NEUEN Pakete werden installiert:
          systemctl
        0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
        Inst systemctl (1.4.4181-1.1 Debian:11.4/stable [all])
        Conf systemctl (1.4.4181-1.1 Debian:11.4/stable [all])
        

        So, just do it. 😉

        #86773
        Member
        stevesr0
          Helpful
          Up
          0
          ::

          Hi male,

          Thanks for checking that it (apparently) is not obviously linked to systemd in antiX-21 stable!

          Then the questions in my mind are:

          1. Is this a useful tool to use in antiX?
          2. Do its functions overlap with other antiX tools?
          3. Does it offer anything that other antiX tools don’t?

          ALL COMMENTS APPRECIATED.

          Beyond that, my focus was in the possible use of this to enable Pipewire’s use in antiX without elogind or libelogind0. But that question really deserves its own thread – or raising in the thread originated in May 2021 by Xecure [https://www.antixforum.com/forums/topic/pipewire-to-manage-audio-in-antix-21/], which I will do when I have composed a list of the approaches I have seen for running Pipewire without systemd.

          stevesr0

          #86842
          Member
          stevesr0
            Helpful
            Up
            0
            ::

            Hi moderators,

            Since it is confirmed that this systemctl from docker-systemctl-replacement ISN’T dependent upon systemd, could this please be marked “solved” and the title changed to “systemctl-replacement NOT dependent upon systemd”?

            Thanks.

            stevesr0

            #86845
            Member
            olsztyn
              Helpful
              Up
              0
              ::

              Then the questions in my mind are:
              1. Is this a useful tool to use in antiX?
              2. Do its functions overlap with other antiX tools?
              3. Does it offer anything that other antiX tools don’t?

              My test environment: antiX 21 Runit, *elogind*-free.
              From my experience, systemctl installs fine with no additional dependencies. I have done just rudimentary testing, so not much value.

              1 – It appears to run fine and lists services along with their status. I will need to do more examination to assess.
              2 – Yes. Systemcrl overlaps with the gui Service Manager tool developed by Xecure. Cross section appears to be the most if not all.
              3 – So far I do not know systemctl tool enough to tell.

              I would just stress that systemctl appears to not require systemd and moreover it does not seem to require *elogind* stuff either.
              Thanks for this discovery…

              Live antiX Boot Options (Previously posted by Xecure):
              https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.