|
|
Sponsored Content
Operating Systems
OS X (Apple)
Apple Perl and LDAP
Post 302407114 by superstructure on Wednesday 24th of March 2010 02:35:11 PM
03-24-2010
Apple Perl and LDAP
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?
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?
|
|
5 More Discussions You Might Find Interesting
1. Solaris
Hi all
I am new to perl-ldap. Trying to install DBD module on sun solaris which has the iplanet51 ldap already installed.
I have got the DBD-LDAP-0.03.tar file , and un packed it.
From the dir DBD-LDAP-0.03 - i tried to do
$ perl Makefile.PL and i got the... (10 Replies)
Discussion started by: kaushi
10 Replies
2. Shell Programming and Scripting
Hi
I'm not a programmer but am muddling through as best I can. I am trying to set up a PostSearchHook for Radiator (RADIUS server), that carries out an LDAP lookup, and, based on the
string returned ("staff" or "student") in the "businessCategory" attribute, will set the $role to be either 40... (3 Replies)
Discussion started by: mikie
3 Replies
3. Shell Programming and Scripting
Hi all,
I'm not even sure a person can do this in perl, seems like you should be able to though.
Here's the error
IO::Socket::INET: connect: Operation now in progress at server_search.pl line 256, <DATA> line 466.
Here's the perl code...
sub ldap_new{
$nl = Net::LDAP->new( "$_" ) or... (3 Replies)
Discussion started by: jtollefson
3 Replies
4. Programming
Hi Perl Guys
I am in need of your knowledge as i am a complete newbie and perl
I need to do pull all the groups from LDAP , and then look at the GID's and if they are not set check for the next available ( i,e increment ) and apply it
I have done this so far that prints out all the... (1 Reply)
Discussion started by: ab52
1 Replies
5. Solaris
I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful.
The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
LEARN ABOUT OPENSOLARIS
disown
disown(1) User Commands disown(1) NAME
disown - ksh93 built-in function to disassociate a job with the current shell SYNOPSIS
disown [job ...] DESCRIPTION
The ksh93 disown command prevents the current shell from sending a HUP signal to each of the specified jobs when the current shell termi- nates a login session. If job is omitted, disown sends the HUP signal to the most recently started or stopped background job. OPERANDS
The following operands are supported: job Specifies the job or jobs on which disown operates. Specify job as one of the following: number Refers to a process ID. -number Refers to a process group ID. %number Refers to a job number. %string Refers to a job whose name begins with string. %?string Refers to a job whose name contains string. %+ or %% Refers to the current job. %- Refers to the previous job. EXIT STATUS
0 Successful completion. >0 One or more specified jobs does not exist. EXAMPLES
Example 1 Disowning a Job The following example disowns job 1: example% disown %1 AUTHORS
David Korn, dgk@research.att.com ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
bg(1), jobs(1), ksh93(1), wait(1), attributes(5) SunOS 5.11 18 Apr 2007 disown(1)