Hey folks -- need my brain refreshed on prolog behavior ...
Trying to figure out if a prolog script would be suitable for
dramatically changing the execution environment -- doing things like NFS
filesystem unmounts or chroot actions so that an incoming job would
execute in the changed environ
Hi Chris,
prolog, job script and epilog are separate processes getting launched by the
shepherd. They get started as the job owner (but I think there also is an
option to start prolog and epilog as root - to be handled with care, of
course). So the prolog is well suited to check things (e.g. wh
I could be wrong Chris but I think the prolog runs in a separate parent/child
process tree than the job. You could put this kind of functionality into a
starter_method where it does the NFS mounts and chroot actions then just runs
the job script. the $JOB_ID will be in the environment and you
The difference between using the starter method and the shepherd wrapper I was
bringing up is that the starter method is run by the shepherd and the shepherd
already assumes a few things to be there, such as the job’s working directory.
If any of those preconditions is not met then starting the
No, the prolog and epilog are run on their own like the jobscript. The
jobscript isn't a child of the prolog.
For such a behavior you would need a starter_method.
Still on vacation - Reuti
Von meinem iPhone gesendet
> Am 08.06.2016 um 12:00 schrieb Chris Dagdigian :
>
>
> Hey folks -- need m
