DAGMan monitors the state of submitted jobs solely by reading the user logs for the node jobs. Things to mention: -*: issues with macros in log file names +*: issues with macros in log file names. Note that this is no longer an issue if the user uses the (default) dagman node log. (implemented in #2807). *: multi-log code truncates files the first time it monitors them (except in recovery mode) *: multi-log code (really, lower-level code) keeps track of where we were in log files, in case we re-monitor them *: we monitor the log file for a node just before submitting it; unmonitor after job is done; special stuff for POST scripts (we write post script terminated event)
