id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 897,Potential temporary directory clash for plugins running through job agents,Jari Häkkinen,everyone,"With modern multi-core machines there will probably be a desire to run several job agents on a single machine. Theses job agents may be running against different BASE servers and this has a potential impact on job execution. Many plug-ins acquire a working directory with code similar to the sample attached below. This is mostly safe but when running more than one BASE job agent on a single host there is a potential clash. A plugin running in different agents (that are running against different BASE servers, if the agents are running against the same BASE server the core guards against this problem ... I hope) may allocate temporary directories with the same (since jobids may match). {{{ protected java.io.File getExecDirectory() { if (execDirectory == null) { execDirectory = new java.io.File (System.getProperty(""java.io.tmpdir"") + java.io.File.separator + getAbout().getName() + java.io.File.separator + job.getId()); execDirectory.mkdirs(); } }}} The java.io.tmpdir returns a default directory (/tmp on linux). We need to facilitate a way to set the temporary directory differently for different job agents. I suggest that we add a configuration option to the job agent properties file.",defect,closed,major,BASE 2.7.1,core,trunk,wontfix,,