X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 29 Feb 2012 11:37 AM by  anon
IDL v8.1+Mac Lion: Problem with Time Machine when using command line
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
29 Feb 2012 11:37 AM
    When launching IDL v8.1 in command line with Mac os X Lion, I got the following warning message: “This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.” One workaround is to type "sudo /Applications/itt/idl/idl81/bin/idl" once (you have Administrator privileges). The error message no longer appears. After having done that, simply launch IDL without Admin privileges and it should work fine.

    Deleted User



    New Member


    Posts:
    New Member


    --
    08 Mar 2012 12:59 PM
    Hi there, To solve or get rid of the time machine error messages: Try starting IDL for the first time as super user, and then close IDL, exit from super-user shell and starting IDL as normal user, i.e: 1- open a terminal and log in as super user 2- in this new super user shell run the IDL setup to setup the environment: . /Applications/itt/idl/idl81/bin/idl_setup.bash See that I used the . operator to source the idl_setup script before the /Application/ (this is if you have a bash shell, if not you will need to run the .ksh or just idl_setup for the csh) 3- Execute IDLDE 4- exit from IDL 5- Exit from the super user shell 6- Run IDL again from a normal user shell. In other words, as an example, try something like the following: sudo -s cd /Applications/itt/idl/idl81/bin . ./idl_setup.bash ./idl Did that help?. That suggestion is the one that worked for many users. Another approach would be: Even if you don't have Time Machine turned on, try toggling it on and off. I hope this helped. Cheers, Fernando

    Deleted User



    New Member


    Posts:1
    New Member


    --
    20 Sep 2012 10:12 AM
    This workaround does not work for users who don't have sudo privileges, which is basically every user in a lab/university setting. This appears to be a user-based fix rather than a machine-based fix. If an admin user logs into a machine and does the above fix, it doesn't solve the problem for other users–only for the admin. If the user has sudo privileges, this fix works, but that's not especially helpful for most users. The other workaround in this Help Article (http://www.exelisvis.com/...essages-in-IDL.aspx) also doesn't work if users need to run IDL on the command line; e.g., if they ssh into a machine to run IDL.
    You are not authorized to post a reply.