Opened 11 years ago

Closed 11 years ago

#167 closed defect (fixed)

Problem rm run_dir_path

Reported by: nvuilsce Owned by: sdipsl
Priority: major Milestone: libIGCM_v2.2 metrics
Component: system Version:
Keywords: Cc:

Description

In change 933 of libigcm_config.ksh, we now remove the directory RUN_DIR_PATH. Before this change, the dir RUN_DIR was removed. There is a check if the RUN_DIR_PATH dir is important or not (with the function check_path), but this check is not enough: When I used this revision of libigcm specifying myself RUN_DIR_PATH, this directory has been deleted at the end of the job.
Would not be possible to find a better solution to the point raised in ticket #141 and to return back to the former instruction
rm RUN_DIR ?

Change History (4)

comment:1 Changed 11 years ago by jgipsl

Proposed solution :

In function IGCM_sys_RmRunDir :
Only delete the directory if RUN_DIR_PATH="default RUN_DIR_PATH". If it is modified by the user in the job, then do nothing or delete the RUN_DIR if possible.

comment:2 Changed 11 years ago by sdipsl

  • Milestone set to libIGCM_v2.2 metrics
  • Owner changed from somebody to sdipsl
  • Status changed from new to assigned

comment:3 Changed 11 years ago by jgipsl

In fact, the sceduler takes car of removing the temporary run directory. Therefor IGCM_sys_RmRunDir can be a dummy one.

Done in commit [964]

comment:4 Changed 11 years ago by sdipsl

  • Resolution set to fixed
  • Status changed from assigned to closed

fix. see r964

Note: See TracTickets for help on using tickets.