From: Phil S. <al...@ca...> - 2003-04-29 21:07:24
|
On Tue, Apr 29, 2003 at 11:56:48AM -0400, Phil Stracchino wrote: > On Tue, Apr 29, 2003 at 05:46:56PM +0200, Kern Sibbald wrote: > > Hello Phil, > > > > I never did understand exactly the reason why this > > was (or perhaps is) happening. In any case, the > > cancel code for 1.30 has been changed a good deal, > > so I would appreciate it if you would test on the > > new version -- already on Source Forge. If it is > > still broken, I'll keep working on it until I get > > it right :-) OK, I just tested this on 1.30. Here's what happened. First, I used the new run functionality to start a postdated job: run A job name must be specified. The defined Job resources are: 1: Babylon5 Save 2: Drazi Save 3: Llioness Save 4: Mabolgamp Save 5: Pond Save 6: Whitestar Save 7: Zocalo Save 8: Babylon5 Restore 9: Llioness Restore 10: Mabolgamp Restore 11: Pond Restore 12: Whitestar Restore 13: Zocalo Restore Select Job resource (1-13): 6 Run Backup job JobName: Whitestar Save FileSet: Windows 2000 Full Set Level: Incremental Client: Whitestar Storage: VXA1 Pool: Full When: 2003-04-29 16:55:39 OK to run? (yes/mod/no): m Parameters to modify: 1: Level 2: Storage 3: Job 4: FileSet 5: Client 6: When 7: Pool Select parameter to modify (1-7): 6 Please enter scheduled start time (return for now): 17:00:00 Invalid time, using current time. Run Backup job JobName: Whitestar Save FileSet: Windows 2000 Full Set Level: Incremental Client: Whitestar Storage: VXA1 Pool: Full When: 2003-04-29 16:55:58 OK to run? (yes/mod/no): m Parameters to modify: 1: Level 2: Storage 3: Job 4: FileSet 5: Client 6: When 7: Pool Select parameter to modify (1-7): 6 Please enter scheduled start time (return for now): 2003-04-29 17:00:00 Run Backup job JobName: Whitestar Save FileSet: Windows 2000 Full Set Level: Incremental Client: Whitestar Storage: VXA1 Pool: Full When: 2003-04-29 17:00:00 OK to run? (yes/mod/no): y (I note that it wouldn't accept just a time, it required a full date and time. This could perhaps use future attention.) Then I listed jobs to see that it was there (non-relevant fields and rows deleted for brevity): list jobs +-------+----------------+---------------------+------+-------+ | JobId | Name | StartTime | Type | Level | +-------+----------------+---------------------+------+-------+ | 166 | Mabolgamp Save | 2003-04-11 02:32:19 | B | I | | 265 | Zocalo Save | 2003-04-29 16:17:28 | B | I | | 266 | Whitestar Save | 0000-00-00 00:00:00 | B | I | +-------+----------------+---------------------+------+-------+ Then I tried to cancel it: cancel Select Job: 1: Whitestar_Save.2003-04-29_16.56.33 Item 1 selected automatically. Confirm cancel (yes/no): yes 2901 Job Whitestar_Save.2003-04-29_16.56.33 not found. 3992 Job Whitestar_Save.2003-04-29_16.56.33 not found. Hmm, curious. So I tried again. cancel job=Whitestar_Save.2003-04-29_17:00:00 Job Whitestar_Save.2003-04-29_17:00:00 is not running. Curiouser and curiouser. status all babylon5-dir Version: 1.30 (28 April 2003) Daemon started 29-Apr-2003 16:50, 0 Jobs run. JobId 266 Job Whitestar_Save.2003-04-29_16.56.33 has been canceled. So, it DID cancel it properly, and did so before the job started, exactly as it should have, but the output makes it appear as though it failed to cancel it. -- .********* Fight Back! It may not be just YOUR life at risk. *********. : phil stracchino : unix ronin : renaissance man : mystic zen biker geek : : al...@ca... : ala...@ea... : ph...@la... : : 2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold) : : Linux Now! ...Because friends don't let friends use Microsoft. : |