Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Permissions on temporary directories provoke failure in feature installations
Permissions on temporary directories provoke failure in feature installations [message #37643] Mon, 19 May 2003 08:09 Go to next message
Eclipse UserFriend
Originally posted by: SUPPRESS.delpiroux.fr.ibm.com

Hi all,



I just want to relate an experience:



If two different UNIX users try to install in the same time, on the same
machine an eclipse feature through an Install/Update perspective, the second
one can't browse the feature site in the Feature Update view. Errors occur;
the jar files can't be read.



It seems that Eclipse creates and uses two temporary directories named
"eclipse" and "platform", under "/tmp" (Linux) or "/var/tmp" (Solaris), and
doesn't delete them. The second user doesn't have the UNIX permissions to
perform the same things, and Eclipse is not able to read the jar files.



The issue occurs also when Eclipse stop with an "abnormal" status.



A possible workaround, delete manually the corresponding directories.



May be, a FAQ or a Bugzilla report is needed ?



Jean-Philippe
Re: Permissions on temporary directories provoke failure in feature installations [message #39611 is a reply to message #37643] Tue, 20 May 2003 08:28 Go to previous message
Eclipse UserFriend
Bugzilla report is probably best. That should be incorrect behaviour in
a shared installation.

Peter
Jean-Philippe Delpiroux wrote:
> Hi all,
>
>
>
> I just want to relate an experience:
>
>
>
> If two different UNIX users try to install in the same time, on the same
> machine an eclipse feature through an Install/Update perspective, the second
> one can't browse the feature site in the Feature Update view. Errors occur;
> the jar files can't be read.
>
>
>
> It seems that Eclipse creates and uses two temporary directories named
> "eclipse" and "platform", under "/tmp" (Linux) or "/var/tmp" (Solaris), and
> doesn't delete them. The second user doesn't have the UNIX permissions to
> perform the same things, and Eclipse is not able to read the jar files.
>
>
>
> The issue occurs also when Eclipse stop with an "abnormal" status.
>
>
>
> A possible workaround, delete manually the corresponding directories.
>
>
>
> May be, a FAQ or a Bugzilla report is needed ?
>
>
>
> Jean-Philippe
>
>
>
Previous Topic:Resources for Plugin-Development
Next Topic:Running WSAD from Command prompt
Goto Forum:
  


Current Time: Fri May 09 01:07:25 EDT 2025

Powered by FUDForum. Page generated in 0.02893 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top