Am 13.01.2012 um 17:33 schrieb Chris Dagdigian:
> Whoa. If there is a tool out there that gives users access to debug and info
> from the spool area I'd love to hear about it and get it out into the
> community. One of the downsides to spool locations is that they are usually
> only accessible to admins.
Because it is on a different machine like a node? The default permissions allow
everyone to read it. As small epilog:
#!/bin/bash
tar -C ${SGE_JOB_SPOOL_DIR%/*} -czf
${SGE_STDOUT_PATH%/*}/${SGE_JOB_SPOOL_DIR##*/}.tgz ${SGE_JOB_SPOOL_DIR##*/}
and you get an archive where stdout is set to.
-- Reuti
> One of my minor gripes about Grid Engine is the lack of debug/troubleshooting
> stuff that is available to non-admin users who don't have sudo or root
> access. One of last good systems providing data to regular users about "why
> is my job not scheduled" is now losing ground since "schedd_job_info=false"
> started being deployed on high-volume clusters.
>
> Even if there is a tool out there that can't be shared it would be great if
> someone could talk about the methods used -- maybe we can gin up an equiv
> utility for the community...
>
> dag
>
>
>
> Dave Love wrote:
>> Not just the administrator, actually. There's stuff which isn't
>> accessible via qacct but can be useful for users to get post mortem
>> information about failures. Mark Dixon has a tool which grovels it
>> (unpublished?, hint).
> _______________________________________________
> users mailing list
> users@gridengine.org
> https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
