OS X (Apple)

We have come across some strange and rather annoying behaviour of Apple's implementation of Perl and LDAP.

I am part of a small scientific software company that provides specialist software for life sciences.

Our internal network is driven by linux servers, but we also have a number of intel Mac's, as many of our customers are using Mac's as well. User accounts on our network are set up and information propogated using LDAP.

Some of our software makes use of some perl scripts.

We have noticed that if we log in to one of the Snow Leopard machines (via ssh) and run our software in the background and then log off before the job finishes, then frequently the job will crash with an error perl: no user <uid>.

If you do not log off, the job completes correctly. This appears to be related to the directory services cache - dscachutil -list will correctly return user information if you are logged in. If you run in the background and log off, it returns nothing.

If, however, we install a different perl install, say Activestate perl, then this problem disappears - we can submit jobs in the background and log off and the jobs finish correctly.

Has anyone else observed this and more importantly, is there a simple solution that doesn't involve installing a new perl distribution?

we had xgrid configuration with our scripts using xgrid on 10.5
and we upgraded our system to 10.6 all of a sudden it stopped working.

Later after many days we learnt that it was because the environment is not carried along;
so i think in ur case try to preserve the environment in ur scripts write all environment varibles relavent in the script itself and try...

i am a novice ...