Search the Community
Showing results for tags 'read-only'.
Found 2 results
Don Lee posted a topic in Retrospect bug reportsI just upgraded a client to 11.5, and none of the backups worked! After a bit of debugging, I figured out that the problem is that the path to the catalog and the members all contain the bullet (option-8) in the path. I moved the sets, updated the sets in the retro console, and it seems to work now. This was an upgrade from 10.5 to 11.5. This was working fine in 10.5, so the bug was introduced at 11.x version.
Don Lee posted a topic in Retrospect bug reportsI try to do my installs with a "system" user who owns and installs all of the applications. In general, I can set all of the applications to read-only, so that even a user who does something pretty dumb can't do much damage. This is also something that is commonly done with enterprise setups, where "approved" applications are kept on a network server, and are strictly read-only because they are shared among many users. The Retrospect console is a single application, and when it is installed according to the implied instructions on the installer disk, the single app is placed in a folder in the /Applications folder, and on first run, parts of that application are moved from the bundle to the folder. Two problems with this: 1. The files so moved are set up with "0777" permissions - that is world read/write/execute. This means that anyone on the system can scribble on them, remove them, rename them, or otherwise screw them up. If I am trying to keep my machine relatively secure this is "bad". 2. If I install the Retrospect console as "admin" and then first launch it as a normal user, these files are not moved from the bundle. I have not yet explored what this means, but it is clear that the difference in behavior will be puzzling to someone in addition to me. My suggestion is that the application should definitely be set up so that if I want to have the folder and all its content be read-only, it should be possible. Bonus points if it is also easy. If the ease of installation of having the bundle contents in the app is important, the step of moving the components to the enclosing folder should be explicit and should request authorization explicitly rater than simply failing as it does now.