Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • systemd.path execution timing

    Posted on

    I am using RHEL7 on a few machines and am trying to utilize the new systemd.path feature for an inotify implementation. It's working out rather well, but I've come across a conundrum. I have a systemd.path unit watching a folder for file changes, and it executes a systemd.service that runs for some amount of time. Say 5 to 15 seconds, depending. So if another file gets changed in that folder and it again attempts to activate the systemd.service, it is already started and so does not execute the ExecStart script. The systemd.service is set to Type=oneshot for this, so perhaps Type=simple would be better suited for this situation. Though I don't know...

    Can anyone provide a better way to accomplish this? I am hesitant to give out details if none are needed, so I tried to explain it without giving as much. So if more is needed, let me know and I will provide.

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat