Daemon logs change last updated timestamp when log or counts aren't changing

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: daemon
    • None

      When watching a long running daemon job, users need to check the job message for progress. If they could rely on the last updated timestamp to reflect real changes, they wouldn't need to repeatedly copy the log to see nothing changed.

            Assignee:
            Chris Hyzer (upenn.edu)
            Reporter:
            Chad Redman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: