| Summary: | starting iac on Linux reports problem Permissions denied for /tmp dir | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | jkubasta |
| Component: | TPTP | Assignee: | Jonathan West <jgwest> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | heatonkm, jptoomey, paulslau, samwai |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
jkubasta
Jonathan, please see if this is reproducible with tptp 4.4 I've tested the following use case on Linux using 4.4. Does the use case fit with the scenario that you are describing? Use Case: As root: 1. Start AC. Run Eclipse, profile the jUnit test. 2. Exit Eclipse. Stop AC from the command line. As non-root: 3. Run Eclipse, profile the jUnit test. (Eclipse should start IAC automatically at this point) 4. Exit eclipse. Using 4.4.0.2, this use case passes. I am able to start and stop the AC server as root, and I am able to start and stop the IAC server as a non-root user. I am able to profile in both step 1 and step 3. The only directores and files created by the AC (as root) are /tmp/IBMRAC/, /tmp/IBMRAC/* (where * are various files), and /tmp/OSSMem*buffer. The /tmp/IBMRAC files, while generated by Root, are RW for all users. All users can read, write, and delete these files at will, ensuring that there will not be any permission problems here. Also, with 4.4.0.2, as far as I can tell, the /tmp/<username>/ files you described are not generated. As per above, works for me w/ 4.4.0.2. Please change the target to the 4.5 iteration when this Bugzilla was resolved. closing |