Hi Winnie,
if I understand your problem correctly then the trick is : how to get
your job recognized as an LCG job, i.e. how can I trick the torque/maui
server into loading all the LCG env vars for *your* job without having
to add stuff to the /etc/profile.d files.
A/The solution might be the pool accounts themselves: I assume you will
have write access to the home directories of the pool accounts; set up
each pool account with a .profile file that loads the missing
/etc/profile.d/glite-env.sh file and your job should have all LCG/glite
env vars set upon entry. Is that feasible at all for you?
HTH,
Jan Just Keijser
System Integrator
Nikhef Amsterdam
Winnie Lacesso wrote:
> Greetings,
>
> We may have access to some WN managed 'externally' which means we have zero
> admin access.
> We cannot write to anywhere but a WN_TAR install area.
>
> The HPC admins (not associated with LCG) are willing to setup pool accounts
> for LCG, so that is taken care of.
>
> It appears that WN links in /etc/profile.d, to glite-env.sh & other
> scripts (which are normally installed in /etc/profile.d, but in the WN
> tarball install, go into our lcg-wn install area) are _absolutely_required_
> for the jobs to get the glite environment set.
>
> The glite-3.1 documentation also seems to insist on links in /etc/profile.d
>
> Is there any workaround so that modification to each WN is _not_ required?
> The remote system is torque/maui.
>
>
> many many thanks!
>
|