Hi Doru, Good question. I'm gonna include the gt-users here for others benefit too.
Yes. You can only control it at the job manager configuration level that sets the directory location for all users. See the JM config "-stdio-log LOG_DIRECTORY" parameter. By using the $(HOME) variable, you get separate locations (directories) for each user. Beware, the JM runs under the user's account, so all user's must be able to write to the location set by that parameter. Also, a new JM log file is created each day, so the log files can be more easily removed/archived/... I'd be curious to know what your specific plans are for this, so we could doc a concrete example for best practices. The JM log location cannot be controlled/set for an individual job. Details are here: http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/admin/#gram5-cmd-globus-job-manager >>> -stdio-log LOG_DIRECTORY Configure the job manager to write log messages to files in the LOG_DIRECTORY directory. Files will be named LOG_DIRECTORY/gram_YYYYMMDD.log. Logging is further controlled by the argument to the -log-levels parameter described below. The LOG_DIRECTORY value can include variables derived from the job manager environment using the same syntax as RSL substitutions. For example, -stdio-log $(HOME) would cause each user's logs to be stored in their individual home directories. <<< -Stu On Feb 17, 2010, at Feb 17, 9:33 AM, Doru Marcusiu wrote: > Hey Stu, > > I was wondering if a particular feature made it in to GRAM5. Some time ago I > was asked if it is possible to define where the GRAM job manager log file > would be written. A reply from you and/or Joe Bester implied that GRAM5 may > provide a a way to do this either for all jobs or for individuals to define > for their jobs. Is that possible in GRAM5? > > Doru > > > > -- > ================================================= > Doru Marcusiu > Assistant Director, Production Cyber Environments > National Center Supercomputing Applications >
