Skip to content
  • Simon McVittie's avatar
    Do not require systemd to have a service file if using it for activation · 3c602d6d
    Simon McVittie authored and Ralf Habacker's avatar Ralf Habacker committed
    With --systemd-activation we special-case the name
    org.freedesktop.systemd1 by assuming that it will eventually connect
    to the bus. With that in mind, we can ignore whether it has a
    .service file, and let it be "activated" regardless.
    
    This fixes a regression test failure on non-systemd systems such
    as the Ubuntu 14.04 OS on travis-ci.org: UpdateActivationEnvironment
    failed, because it tried to update the (fake) systemd environment,
    but because systemd was not actually installed, there was no
    service file for it in the system's search paths. We could address this
    by placing a dummy service file with Exec=/bin/false in our search path
    like the real systemd does, but it seems cleaner to not require this;
    this would eventually enable the real systemd to stop installing
    that dummy service file.
    
    This would not happen outside the regression tests, because there is
    no sense in using --systemd-activation without systemd installed.
    
    Bug: https://bugs.freedesktop.org/show_bug.cgi?id=93194
    
    
    Reviewed-by: default avatarRalf Habacker <ralf.habacker@freenet.de>
    3c602d6d