| Cannot inject update-sites, cannot find the correct config? [message #1385838] |
Wed, 11 June 2014 10:45  |
Eclipse User |
|
|
|
Hi,
i've got a problem, when starting eclipse with sudo:
find: "/root/.eclipse": Datei oder Verzeichnis nicht gefunden (which means file or directory not found)
find: "/root/.eclipse": Datei oder Verzeichnis nicht gefunden
W: Cannot inject update-sites, cannot find the correct config.
I have to start Eclipse as root, since i use IO-functions which require root-priviliges while running or debugging within Eclipse. Is there any startup parameter, by which i can tell eclipse to use a different startup dir oder ini-file?
Kind regards
Frank
[Updated on: Mon, 23 June 2014 05:09] by Moderator |
|
|
|
|
| Re: Cannot inject update-sites, cannot find the correct config? [message #1387078 is a reply to message #1386949] |
Mon, 23 June 2014 19:27  |
| Eclipse User |
|
|
|
On 06/23/2014 02:47 AM, Frank Mising name wrote:
> Nitin, thanks for your support, but I'm sorry: I'm no Unix-Expert. What
> should the shell script achieve? From my understanding, Eclipse takes
> the home-dir of the user who starts it. I'm not sure, wether it makes
> sense to change root's home-dir.
> Kind regards
> Frank
The root user has a very different environment (environment variables
like PATH, etc.) than your user.
One does not typically run Eclipse as root. It's somewhat odd that you
a) are no UNIX expert, but b) know that you need root access. What
exactly are these IO functions?
Whatever the case, the shell script would establish your root identity
while setting up the environment so that everything can be found.
One way to make this easier would be to stop trying to manage Eclipse as
a multiuser application and just use a private copy (that isn't going to
try to find /root/.eclipse). I believe that Eclipse knows it's a
"multiuser" application when the folder it's in is read-only or not
writable by the launching user.
I've never done this, but I hope I'm helping.
Cheers
|
|
|
Powered by
FUDForum. Page generated in 0.19877 seconds
Home