#6 temp.env & privilege related issue

closed
Suresh Malan
None
5
2009-10-22
2009-09-10
Anonymous
No

Currently at the start of jensor, temp.env gets created at the location from where jensor gets invoked (for say in application server main process folder). This will give exception if that invokation folder does not have write privilege. Can we create temp.env always under "JENSOR_HOMe\bin". As this would reduce issue with privileges.

Discussion

  • temp.env itself is used for finding out value of JENSOR_HOME. So writing temp.env to JENSOR_HOME\bin is out of question. However we can look into other options like writing to temp directory or writing to user's home directory where user has write permissions.

     
    • milestone: --> Next Release (example)
    • assigned_to: nobody --> suresh_malan
    • status: open --> pending
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
    • status: pending --> closed