CCS 5 creates folders as Administrator under Win7

CCS Version: 5.1.0.09000

HI Randy,

there are some know items with privileges for sure.  Ususally we always say to install and run CCS with administrator privileges.

- Have you asked IT if they can set up your colleagues with an exception for CCS launch?  I am not deep windows expert, but I am wondering whehter there is a way to get permissions on a single program to launch as admin without having those privileges for the full machine

- what directory do you install CCS into?  Keep your workspaces in?   This might make a difference as well and again ... could access be granted for those folders alone.  For example win 7 has interesting permissions on the program files directory.  Also, there are also different permissions for folders under a user tree.

Please keep us informed.

Best Regards,

Lisa

Hi Lisa,

That was QUICK! Thanks!

I set up my projects under C:/cygwin/home. I have cygwin installed and it is convenient for me to keep them there instead of the usual workspaces area. Just FYI.

--Randy

Lisa, here are some more details:

CCS was installed by a user with administration privileges.

It was installed into the default directories recommended by the installer.

Lisa, one more thing: it is unlikely that I will be able to convince IT to allow me to have administrator privileges (unfortunately!) - they are very strict here that way.

Hi Randy,

ok, if you are not using the program files directories that is a good thing.

Have you tried things like right clicking and selecting "run as administrator"?   Have you started enquiring about per program or per folder permissions?   I am not sure that anything in CCS can change so hopefully we can find a good work around for you.

Best Regards,
Lisa

Lisa,

No matter how many work-arounds you provide, it is pretty clear that this is a CCS bug. I am therefore disappointed to hear you state, "I am not sure that anything in CCS can change." It should change: TI should fix the bugs! It is a simple matter to change the code so that it creates the Release folder with the same ownership and permissions as the parent folder.

As I have already stated, I do not have administrator privileges, therefore "running as administrator" is not an option, and our IT department will not give administrator privileges to normal users.

--Randy

HI Randy,

I fully understand and can put it forward to development here/file it, but I myself can not make any decisions or promises going forward.

Did any of the suggestions help?

Best Regards,
Lisa

Lisa, since you're last name isn't Templeton, that's all I can ask :). Thank you.

--A former TI Contractor (Smart meter/Susan Yim's group)

PS: It is hard to troubleshoot since it's an intermittent problem - it doesn't happen consistently.

Hi Randy,

I doubt that this is a CCS bug.  We use a Java API to create directories, and that API doesn't give us any control over permissions (for a good reason).  The fact that the problem is intermittent also suggests that the problem can't be in CCS, as we use the same API consistently.  

Please try to see if you can find a workaround for this problem in your environment.  Try placing your projects somewhere other than the cygwin install directory - usually in Windows 7, user writeable artifacts should be placed in the user's "Documents" or C:/User/<username>/ directories, or a global directory which you've created with your user privileges.  In general, I wouldn't recommend placing your projects in a third party product's install directory, because if you uninstall/upgrade that product, you may lose your files.

Let us know if you find a solution.

Thanks,

- Baltasar

Baltasar:

Why should I find a "workaround?" Fix the problem!

An operating system provides a file system for a reason: to allow users to manage their files in the way they see fit. How they manage them is no concern to an application.

--Randy

PS: As I see it, basing your application on a library or API that doesn't work correctly is still your problem.

--Randy

Randy,

I understand you are getting frustrated here and some of our responses haven't been the best.  

If CCS is running with User privileges then under normal circumstances Windows is not going to create a directory with admin privs and place items in the folder.  That is why the opinion has been expressed here that this is not a CCS bug.  Our code is calling an AP which in turn asks the OS to create a directory.  There is no manipulation of permissions going on.  The API we call is a JAVA API we call that as it abstracts the OS.  The JVM then makes the appropriate call for the OS.  This same API we are calling is used by all JAVA applications, nothing flaky here. 

The red flashing light that goes off for me when I read this thread is Cygwin.  Are you invoking CCS from a cygwin shell?  As Baltasar mentioned do you see the same behavior with the project is outside of your Cygwin home folder?

Regards,

John

John,

Well somehow an Administrator-owned Release/ folder is being created by someone. Our project files are maintained in a subversion repository, and I've verified the versioned folders do not include Release/. So it is not my subversion client that is creating the Release/ folder. It is my understanding that CCS creates that directory the first time the project is built if it doesn't already exist. Hence my conclusion that this is a CCS problem.

No, I am not invoking CCS from a cygwin shell. Here is my normal flow: 1) I start CCS from the start menu, 2) I import the project from my c:/cygwin/home/... directory, 3) I build my project. 

Note that concerns that my project will be wiped out with an upgrade are baseless: all the project files are maintained in svn. The working copies on my local machine in the cygwin folders are just temporary. 

--Randy

PS: The reason I want my files under cygwin is that my main interface to the files is via the cygwin version of emacs. If I place the files in c:/cygwin/home, then under cygwin/emacs I access them as /home/... If I were to place them in the usual workspace folder it would be something like /cygdrive/c/Documents\ and\ Settings/yates/workspaces/...  - you see the issue?

--Randy

Randy,

They don't need to go under your user folder just try somewhere other than the cygwin folder (eg: c:/test)

Regards,

John

UPDATE:

As I stated, this problem is intermittent. I checked out my project files to a folder under C:/test (which is owned by me). I was able to build without a problem, and the Release/ folder was created with me as the owner. Then I deleted the original project files (the ones that caused this issue in the first place) that were under c:/cygwin/home. (Our IT department had to help since the Release/ folder was owned by Administrator.) I then re-checked out the same project to the same place, with exactly the same names, and was able to build without a problem, and the Release/folder was created with me as the owner this time.

So, the problem is difficult to reproduce. One cannot conclude from this simple test whether the problem is the cygwin path or not. There is no reason I can think of the cygwin path would make any difference - the cygwin and home folders are both owned by me.