Uploaded image for project: 'CFEngine Community'
  1. CFEngine Community
  2. CFE-2214

expireafter for daemons is set to 0 or 1

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: cf-serverd
    • Labels:
    • Platform:
      N/A

      Description

      Expireafter for daemons should be infinite. But the current value for some daemons (for example @cf-monitord@ and @cf-serverd@) is set to 0 or 1, which means that once a new process is executed, it kills and replaces the old one.

      BTW ifelapsed should be zero (I believe that is the case), because after a daemon has exited, we don't want to wait in order to restart it.

      Example buggy code for cf-serverd in @cf-serverd-functions.c:AcquireServerLock()@:
      <pre>
      TransactionContext tc =

      { .ifelapsed = 0, .expireafter = 1, }

      ;
      return AcquireLock(ctx, pp->promiser, VUQNAME, CFSTARTTIME, tc, pp, false);
      </pre>

        Attachments

          Activity

            People

            • Assignee:
              a10038 jimis (Dimitrios Apostolou)
              Reporter:
              a10038 jimis (Dimitrios Apostolou)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Summary Panel