We run Debian Sarge, our current account script:
- Uses getpwnam to check if an account exists
- If not, adds account info to LDAP
- Uses getpwnam to get the $uid and $gid to chown mail spool
While the script is running, the second getpwnam fails. This behavior does not occur with file (/etc/passwd) based accounts.
The problem also occurs with User::pwent
If it turns out that this isn't a problem with my understanding, I can think of a few (ugly) ways to work around the problem. If it is a real problem, any thoughts on the best way to report the bug to the OpenLDAP (?) Pam (?) glibc (?) people would be helpful.
#!/usr/bin/perl -w
getpwnam("test")
or warn "account doesn't exist yet... (expected)";
# code to add LDAP account here brings out problem
# code to add to /etc/passwd account doesn't
getpwnam("test")
or warn "shouldn't see this but we do\n $!";
(system("chown test.test /tmp/file")==0)
or warn "this also fails"
# this works but is ugly
warn `getent passwd | grep test`,"\n";
# $! eq 'No such file or directory'
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|