<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Allow multiple Unit= entries in timer units"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=82180">82180</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Allow multiple Unit= entries in timer units
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>freedesk.apriori@spamgourmet.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr></table>
      <p>
        <div>
        <pre>It would be convenient if timer units could, in analogy to multiple ExecStart
entries in services, specify multiple Unit= values, which are then run
sequentially (or perhaps in parallel, when specified by some syntax) when the
timer triggers.

While one could achieve this by having a single Unit= in the timer and multiple
ExecStart= in the associated service, it might not always be prudent or
desirable to implement this at the level of .service files. E. g., when the
services combined in one timer are usually used in isolation; combining them
would then require duplication parts of those service units, whereas a single
timer with multiple Unit= entries would be cleaner.

This would also be one way of addressing the problem that timers currently
cannot be orchestrated to run sequentially (cf.
<a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Allow for random startup delay (or even spread) in timer units"
   href="show_bug.cgi?id=82084">https://bugs.freedesktop.org/show_bug.cgi?id=82084</a>).</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>