Hello,

if the file "%{sge_home}/util/install_modules/inst_template.conf" is marked as config file, it won't get overwritten during an rpm upgrade. I think this should be the default behaviour...

best regards,

Florian La Roche

--- gridengine.spec +++ gridengine.spec @@ -249,6 +251,7 @@

%{sge_home}/mpi %{sge_home}/pvm %{sge_home}/util

+%config %{sge_home}/util/install_modules/inst_template.conf

%{sge_home}/utilbin %{sge_mandir}/man1/*.1.gz %{sge_mandir}/man5/*.5.gz

From Thimo Neubauer. ​http://arc.liv.ac.uk/pipermail/sge-discuss/2011-November/000190.html:

Hi!

I've got a problem with Grid Engine on Windows hosts and wanted to
check whether I'm missing something obvious or encountering a
bug. What I'm experiencing is that the usual GE environment variables
(including PE_HOSTFILE) aren't set when "-l display_win_gui=true" is
set. You can see the effect when you qsub

  /dev/fs/C/Windows/System32/cmd.exe /c "set S > c:\env.txt"

where "c:\env.txt" will contain all environment variables starting
with "S". With "display_win_gui=true" I don't see a single SGE_*
variable; without I get  SGE_CELL, SGE_ARCH, etc. like I expected. I'm
working with sources I've taken from darcs in June. Before upgrading
to 8.0.0c I've decided to review the diff: nothing in there seems like
fix to me.

I've traced the sources so far as to understand that
SGE_Helper_Service is used for the display_win_gui mode and that it
constructs an environment for the process. However I don't understand
the architecture enough to see how execd/shepherd pass information
into the helper.

My use case is a test of our Windows-GUI based application which can
initiate MPI computations. Without PE_HOSTFILE I fail to see how I can
find out which hosts I can use for the MPI run :)

From ​http://wikis.sun.com/display/gridengine62u7/Release+Notes

A new environment variable for DRMAA applications is introduced. If "SGE_DRMAA_ALLOW_JOB_ERROR_STATE" is present in the environment of the shell which starts the DRMAA application, then, in case of job errors, the job will enter the ob error state. Without this environment variable DRMAA jobs are not allowed to enter the job error state (which is the default behavior in earlier versions).