[Greg McKaskle]

If it makes you feel better, we have been talking about you, just not to you. We are engineers too, after all.

I had something similar happen to me during the beta, but I think I caused it by putting some things on the target using ftp and having a folder owned by admin that wouldn't allow other tools to write to their normal location.

Brad is looking to see if the tools may be creating something like this.

If you see the situation again and want to do some sleuthing, shell in and run the following...

find /home/lvuser ! -user lvuser -print

This will show all files under lvuser that are not owned by it. I have two files like that on my roboRIO, but nothing concerning. A directory could really foul up a deployment, and that would help the Eclipse-meisters know where to start looking. And that presumably is what you would chown to lvuser in order to get around it.

Greg McKaskle