Retrospect does not quit when finished

[garryggreen]

In V6, I had Windows Scheduled Tasks execute a BAT file that would run (2) Retrospect Run Documents consecutively; I had the Media Timeout set to 1 minute and QUIT upon termination; when the first execution ended, the BAT file would regain control and execute the 2nd Run Document.

 

In V6.5, the Media Timeout and QUIT options are apparently not being honored. Is this a bug, or is there an option I'm missing. Thanks

 

Garry G. Green

[natew]

Hi

 

Check the lookahead time settings in Retrospect. The minimum value is 1 hour. Which means if Retrosepct sees a script scheduled to happen within 1 hour from now it will stay open and wait rather than close.

 

Nate

[garryggreen]

Look ahead time is not a problem since there are NO scripts at all scheduled in Retrospect.

[churchtown]

I saw something that might be appropriate in the products area for changes between v6 and v6.5:

 

http://dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27938

 

Immediate Operations

All Retrospect 6.5 immediate operations run in unattended mode. The Unattended options Dropdown Menu in the Retrospect toolbar uses the look ahead time in Configure>Preferences to determine behavior upon completion.

 

best wishes, Robert

[churchtown]

[update]

 

This seems to be a bug/buglet. I certainly see something similar here with a manually invoked Run Doc that always remains up after 'finishing'. Can this be considered as being reported in this thread or is there a dedicated bug reporting trail?

 

 

best wishes, Robert