Thank you guys for the advise! Best regards,
Taras On Mon, Jan 25, 2016 at 5:54 PM, William Hay <[email protected]> wrote: > On Mon, Jan 25, 2016 at 01:05:50PM +0100, Fritz Ferstl wrote: > > One could also wrap the shepherd if what you wanted to do is check for > the > > working directory and potentially create or mount it if it isn't there > yet > > before exec'ing the real shepherd. All so called methods (prolog, > starter, > > pe-*, etc) are run by the shepherd. So by wrapping it you can precede > all of > > that. > > > If you go with Fritz's Solution there is even a nice shepherd_cmd config > option > in the sge_conf you can use to point at your wrapper. > > William > > Cheers, > > > > Fritz > > > > William Hay schrieb: > > >On Mon, Jan 25, 2016 at 01:33:09PM +0300, Taras Shapovalov wrote: > > >> Hi guys, > > >> We have faced with uncharacteristic (for other workload mangers) > behavior > > >> of OGS 2011.11p1 (probably UGE has the same behavior, not sure > yet). > > >> Prolog is called always after stderr/out files are created. This > means > > >> that if prolog creates some directories that are not exist before > and std > > >> files should be put there, then the job is put in a failure state. > > >> Is it possible to switch such behavior somehow? I think if prolog > starts > > >> before any sgeexecd's actions related to a job then the prolog > would be > > >> much more useful. > > >> Any idea is appreciated! > > >> Best regards, > > >> Taras > > > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
