Feature summary (what you would like to be able to do and where):
Add a --log-dir parameter to the toolforge-jobs run command which would specify the path of a directory in which the user wants the log files associated with the invoked job to be stored in.
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
With the grid engine, we have this option; a user can submit a job like jsub -N "somename" -o ./err/somename.out -e ./err/somename.err ./jobs/somename.sh.
If someone is really confident, they can even redirect the job output to /dev/null so as to not waste any disk space and need to do no cleanup later on.
Benefits (why should this be implemented?):
This helps users keep their tool's home directory from getting cluttered by tons of log files.
This also helps the new toolforge job framework to more closely resemble the grid engine, which will help with the transition.