|
I've seen this behavior if you have multiple SDs scheduled (I use cron to run scripts), and the first one fails (see my new post regarding scripts detecting errors), for example with an I/O error. I think the SD status stays up even thought the script ends (my drives get dismounted, my custom log gets posted, etc.), along with the "schedule" window.
Then when the second script fires up, as dnanian mentioned, SD then does not quit, but leaves its final window up. This behavior is what clued me into the I/O error, since the "on error" condition did not activate in my script.
So, check for some error in the log which kept your SD active at the end of its or a prior scripts activation.
Ed
|