| Summary: | Admin password is in the process command line | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Denis Roy <denis.roy> |
| Component: | Client | Assignee: | Project Inbox <e4.orion-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aniefer |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Denis Roy
Do you start the server using 'eclipse' or do you invoke java directly? If you are starting "eclipse", it looks like the vm is being forked in a second process. It is possible to use java in-process instead, you would need to specify -vm with a path to the libjvm.so file eclipse -vm /usr/java/jdk-1.6.x86_64/jre/lib/amd64/server/libjvm.so In this case, the password wouldn't be on the common line in top/ps (In reply to comment #1) > Do you start the server using 'eclipse' or do you invoke java directly? Good question. I have an elite crew of skilled Java gurus doing server administration for me, so I'll have to ask them ;) Note this is just the default admin password, and only has to be specified when no admin account exists yet (once the admin account has been created the administrator can change it to something else). I think Boris just left it in the eclipse.ini file so you would know what the password is. Andrew's change makes sense as well. We can also consider moving this property to the server configuration file where we set the authentication, etc. It would be easier to administer if all these things are in the same place. The only goofy problem with that is that the administrator then has to manually create the funny directory structure (serverworkspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/...etc.. If we don't consider moving the option to the serve configuration, this bug can be closed. This was fixed with the switch to orion.conf file. |