We are in the process of developing a gridwatcher utility that is launched
in the background from the prolog script. The intent is to have a
process monitor various aspects of the job and store or report on them.
It currently determines the pid of the shepherd process then watches all
the children processes.
Initially it will be watching memory usage and if a job begins using more
physical memory than requested, the user will be notified. That's where
my question comes from.
Is there any way in the prolog to get access to the hard_request options
besides using qstat?
What I'm currently doing:
cmd = "bash -c '. #{@sge_root}/default/common/settings.sh && qstat
-xml -j #{@number}'"
I have thought of possibly setting an environment variable via a jsv script
that can be queried by the prolog script. Is this a good idea? How much impact
on submission time does jsv_send_env() add?
Any one else doing anything like this have any suggestions?
The end goal is to have a utility that users can also interact with to
monitor their jobs. By either setting environment variables or grid
complexes to affect the behavior of what is being watched and how they
are notified.
Thanks.
--
-MichaelC
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
