bmswalla Posted August 14, 2003 Report Share Posted August 14, 2003 I'm running two backup server scripts set for the same execution time frame: 11PM-7AM. Retrospect launches normally while unattended, and completes the backup fine. However, every morning around 8AM, I find the machine with the backup server window (and retrospect) open behind the OS X login window, displaying its "inactive" status. How do I get Retrospect to quit after the backups are complete and the scripts become inactive? Should it be able to do this? thanks in advance Brian Link to comment Share on other sites More sharing options...
bmswalla Posted August 28, 2003 Author Report Share Posted August 28, 2003 ^bump^ Does anyone else here run the Backup Server under OS X? Does it quit while unattended? Link to comment Share on other sites More sharing options...
natew Posted August 28, 2003 Report Share Posted August 28, 2003 Hi Have you set the global schedule for Retrospect in the Preferences? How about setting the look ahead time to 1 hour? Nate Link to comment Share on other sites More sharing options...
gwinterboer Posted August 28, 2003 Report Share Posted August 28, 2003 Yes. I have a flat panel iMac and Xserve running 10.2.6 and sometimes I will find Retrospect as quit altogether and have to reboot and relaunch the Retrospect. I have asked Dantz about it and of course they don't know and want to charge me to have them figure it out. Has anyone fixed this? Tx GW Link to comment Share on other sites More sharing options...
CallMeDave Posted August 28, 2003 Report Share Posted August 28, 2003 Quote: I have a flat panel iMac and Xserve running 10.2.6 and sometimes I will find Retrospect has quit altogether and have to reboot and relaunch the Retrospect. - Why do you say you have to reboot? - Are you running Scripts? The default action for Retrospect is to quit after Scripts complete. - What version of Retrospect are you using? - Is there a Retrospect crash log generated in /Library/Logs/CrashReporter/ ? >I have asked Dantz about it and of course they don't know >and want to charge me to have them figure it out. Tech support is free when the program is new, and costs money after you've owned and used it for a while. If you want others to offer suggestions you'll need to be clear about exactly what you're seeing. It's not always easy to "figure it out" without all the relevant data! Link to comment Share on other sites More sharing options...
bmswalla Posted August 30, 2003 Author Report Share Posted August 30, 2003 Quote: natew said: Have you set the global schedule for Retrospect in the Preferences? How about setting the look ahead time to 1 hour? Thanks for the tip, Nate. I had tried setting the look ahead to only 1 hour, but not changing the "global schedule". I skipped it before because the pref window indicated that the global schedule only affects default execution times for scripts that are *not* backup scripts. That reference (I didn't quote it exactly) is a little unclear (does it affect backup scripts at all?). But I'll go ahead and try it tonight anyway and report back. Gary, your problem is significantly different from mine. I'm sorry I don't have any specific suggestions. You should try posting about it in a new thread for the most help and/or visibility. And as Dave suggested, more information would also be useful! There is a lot of good tech info on this site. Have you tried searching the available articles? Brian Link to comment Share on other sites More sharing options...
bmswalla Posted August 30, 2003 Author Report Share Posted August 30, 2003 Retrospect still doesn't quit the backup server while unattended. I have no problems when I run a regular "backup" script. However, I would like to use a backup server script because I wish to enable client-side control over the backup process - such as postponing the backup, or requesting it ASAP. It is simply much more flexible for the client computer. Unfortunately, the server takes over the computer it is run on, and doesn't let go until someone enters an admin password (any numerous mouse clicks) to quit it. This is very annoying for those users. Maybe the backup server scripts were never designed to be used in this way, but from reading the manual I was given the opposite impression. darn. any other suggestions would be greatly apreciated! Link to comment Share on other sites More sharing options...
CallMeDave Posted August 30, 2003 Report Share Posted August 30, 2003 Quote: the server takes over the computer it is run on, and doesn't let go until someone enters an admin password (any numerous mouse clicks) to quit it. If you don't want password protection for auto-execution, disable it in Special->Preferences->Security If you don't want Retrospect to confirm stopping the backup server, disable it in Special->Preferences->Run Control Dave Link to comment Share on other sites More sharing options...
bmswalla Posted August 31, 2003 Author Report Share Posted August 31, 2003 Thanks, Dave. However, both of these issues are secondary. What I really want is for the Retrospect backup server to quit at a defined time (such as when it is scheduled to be inactive). I can't seem to find out whether this is possible or not. I'm puzzled, because the backup server will launch while unattended. So why won't it quit while unattended??? Regarding your suggestions 1) Accoring to the preferences dialog, the security setting you mention does not affect automatic execution. That setting only appears to affect manual launching of the program. Regardless, I had already disabled the "require authentication" option, and it does not help in this case. Here, the user logs in after Retrospect has launched (as root when no user was logged in). Retrospect apparently inherits the user's identity as its owner, and subsequently requires their admin password in order to accept *ANY* input, including quitting or simply repositioning a window on screen. As a side note, you can interact with restrospect while no user is logged in (if you can click on its windows behind the login screen) but the root password is required. 2) As far as run control, that's only one click saved - and I would prefer to leave it enabled! Brian Link to comment Share on other sites More sharing options...
CallMeDave Posted August 31, 2003 Report Share Posted August 31, 2003 Quote: you can interact with restrospect while no user is logged in (if you can click on its windows behind the login screen) but the root password is required. If Retrospect auto-launches without any Aqua user logged in, accessing Retrospect will display the authentication dialog box with the Name field populated as 'root.' But that field can be edited to any valid user in the admin group, and that user's password will be adequate to authenticate Retrospect. Link to comment Share on other sites More sharing options...
bmswalla Posted September 2, 2003 Author Report Share Posted September 2, 2003 That makes sense, although I never tried it. for me it is easiest to just give it the root pw. However, we digress... Is anyone else here employing backup server scripts? Brian Link to comment Share on other sites More sharing options...
j-beda Posted September 16, 2003 Report Share Posted September 16, 2003 Quote: CallMeDave said: If Retrospect auto-launches without any Aqua user logged in, accessing Retrospect will display the authentication dialog box with the Name field populated as 'root.' But that field can be edited to any valid user in the admin group, and that user's password will be adequate to authenticate Retrospect. Not in my situation - for me it did not require any authentication (I do not have the "require auth" checkbox checked). This leaves a pretty big security hole, since one can access Retrospect's menus, including "help", which launches a web-broswer (Safari), which can then launch the finder, as root it seems, by typing in a URL such as ftp://apple.com. What would be nice is if Retrospect were to launch itself hidden in the background when no user was logged on. Heck, this might be nice for any time that it auto-launches. Link to comment Share on other sites More sharing options...
CallMeDave Posted September 17, 2003 Report Share Posted September 17, 2003 Quote: This leaves a pretty big security hole The relevant setting in Retrospect is under the "Security" heading. If you choose to disable this level of security, the hole is one you dug for yourself. There _was_ a real hole that showed up in one of the 5.0.x versions, where the Apple Menu could be accessed while the authentication challenge window was present. This has been fixed in version 5.1 Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.