What steps will reproduce the problem?
1. Launch MSU.app manually
2. Change an optional install.
3. Click 'update'
4. Press 'stop' during the munki status run
5. [results are displayed ... perhaps they shouldn't be]
6. Click 'update'
7. Munki-status run stops promptly, and log file indicates it is because the
stop button was pressed. (it hasn't been, it was pressed in the last run)
What is the expected output? What do you see instead?
A stopped run probably shouldn't take the user back to the results pane, but
exit (or provide a popup then exit).
If it is legitimate that munki-status be run multiple times (in the same
running instance of MSU.app), it shouldn't remember that the stop button was
pressed between munki-status runs.
Original issue reported on code.google.com by rrmiddleton@gmail.com on 28 Nov 2010 at 1:30
Original issue reported on code.google.com by
rrmiddleton@gmail.com
on 28 Nov 2010 at 1:30