SGE_COSHEPHERD(8)

πŸŽ€ NAME πŸŽ€

okay so bestie, meet sge_coshepherd β€” the Grid Engine single job-controlling agent πŸ’– that's it, that's the whole identity. it's giving "small but mighty" and honestly? we love her for it 🫢


✨ SYNOPSIS ✨

sge_coshepherd

no flags, no args, no drama. she just arrives πŸ’…


🌸 DESCRIPTION 🌸

so here's the tea, bestie β˜• β€” sge_coshepherd is needed to run the token manipulation executables if Grid Engine is running in an AFS environment. that's her whole gig. AFS bestie behavior only πŸ¦‹

she gets started by the shepherd process, and the way that she's literally in the same PAG (process authentication group) as the shepherd and the user's job?? iconic. same group chat, same vibes, no cap πŸ”₯

and what does she do in there? she babysits AFS tokens πŸ‘‘ exactly as specified by set_token_cmd and token_extend_time of sge_conf(5). like, she's the token nanny. the token au pair. she's not leaving until the job's done, periodt πŸ’…βœ¨


πŸ’œ SEE ALSO πŸ’œ

  • sge_shepherd(5)
  • sge_conf(1)

See sge_intro(1) for a full statement of rights and permissions. legal besties, we see you 🫢


okay that's the whole page bestie, mwah πŸ’‹ this was SGE 8.1.3pre, dated $Date: 2011-05-14 13:06:11 $, and it came to you straight from the Grid Engine Administrative Commands section β€” go be a good coshepherd, ily, bye πŸŽ€βœ¨