Ticket #4 (new Enhancement)
Opened 9 months ago
launchd.plist man entry needs clarification for StartInterval
| Reported by: | levi@… | Owned by: | |
|---|---|---|---|
| Priority: | 5: Not set | Milestone: | |
| Version: | Severity: | Other | |
| Keywords: | plist man documentation docs | Cc: |
Description
Presently, the man entry contains:
StartInterval <integer> This optional key causes the job to be started every N seconds. If the system is asleep, the job will be started the next time the computer wakes up. If multiple intervals transpire before the computer is woken, those events will be coalesced into one event upon wake from sleep.
Which, if I may suggest so, could be improved to be less ambiguous. Specifically, this does not tell the reader if the job will be started every N seconds, if it is already running or not. Through experimentation I was able to discover that if the job is presently running when the interval expires, no new job will be initiated, and no queuing effect will occur either. This happens to be the behavior /I/ wanted for my purposes, but the documentation is not clear on this matter and there is no mention of a way to allow spawning of multiple jobs should the intervals overlap, etc.
Note: See
TracTickets for help on using
tickets.