Prevent systemd unit from starting if a certain other unit is running












1















I have two systemd services application.service and feh@.service.
application.service is enabled and usually running.
feh@.service is not enabled and started only manually and has a Conflicts=application.service entry.



I want to achieve, that if application.service is running and I start an instance of feh@.service, that application service terminates.
This is currently working due to the Conflicts=application.service entry mentioned above.



However, a data synchronization service periodically restarts application.service via systemctl restart application.service remotely.
I would like this to fail if, and only if, feh@.service is running.
Currently this will shutdown the feh@.service instance and start application.service.
I could not find anything related to this in the official documents of systemd.



Background info:



I cannot let the remote service check for feh@.service because this only exists on a few machines (it is an exceptional configuration) and is not part of the usual infrastructure.
I also do not want to stop the service, since it also controls other devices that may not run feh@.service.










share|improve this question





























    1















    I have two systemd services application.service and feh@.service.
    application.service is enabled and usually running.
    feh@.service is not enabled and started only manually and has a Conflicts=application.service entry.



    I want to achieve, that if application.service is running and I start an instance of feh@.service, that application service terminates.
    This is currently working due to the Conflicts=application.service entry mentioned above.



    However, a data synchronization service periodically restarts application.service via systemctl restart application.service remotely.
    I would like this to fail if, and only if, feh@.service is running.
    Currently this will shutdown the feh@.service instance and start application.service.
    I could not find anything related to this in the official documents of systemd.



    Background info:



    I cannot let the remote service check for feh@.service because this only exists on a few machines (it is an exceptional configuration) and is not part of the usual infrastructure.
    I also do not want to stop the service, since it also controls other devices that may not run feh@.service.










    share|improve this question



























      1












      1








      1








      I have two systemd services application.service and feh@.service.
      application.service is enabled and usually running.
      feh@.service is not enabled and started only manually and has a Conflicts=application.service entry.



      I want to achieve, that if application.service is running and I start an instance of feh@.service, that application service terminates.
      This is currently working due to the Conflicts=application.service entry mentioned above.



      However, a data synchronization service periodically restarts application.service via systemctl restart application.service remotely.
      I would like this to fail if, and only if, feh@.service is running.
      Currently this will shutdown the feh@.service instance and start application.service.
      I could not find anything related to this in the official documents of systemd.



      Background info:



      I cannot let the remote service check for feh@.service because this only exists on a few machines (it is an exceptional configuration) and is not part of the usual infrastructure.
      I also do not want to stop the service, since it also controls other devices that may not run feh@.service.










      share|improve this question
















      I have two systemd services application.service and feh@.service.
      application.service is enabled and usually running.
      feh@.service is not enabled and started only manually and has a Conflicts=application.service entry.



      I want to achieve, that if application.service is running and I start an instance of feh@.service, that application service terminates.
      This is currently working due to the Conflicts=application.service entry mentioned above.



      However, a data synchronization service periodically restarts application.service via systemctl restart application.service remotely.
      I would like this to fail if, and only if, feh@.service is running.
      Currently this will shutdown the feh@.service instance and start application.service.
      I could not find anything related to this in the official documents of systemd.



      Background info:



      I cannot let the remote service check for feh@.service because this only exists on a few machines (it is an exceptional configuration) and is not part of the usual infrastructure.
      I also do not want to stop the service, since it also controls other devices that may not run feh@.service.







      systemd dependencies






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 29 at 13:27









      Jeff Schaller

      41.2k1056131




      41.2k1056131










      asked Jan 29 at 12:24









      Richard NeumannRichard Neumann

      516312




      516312






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497438%2fprevent-systemd-unit-from-starting-if-a-certain-other-unit-is-running%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497438%2fprevent-systemd-unit-from-starting-if-a-certain-other-unit-is-running%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

          is 'sed' thread safe

          How to make a Squid Proxy server?