vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| All, I am running a project to build an ldap server to be used for user authnetication, for sudo administration and for SSH key management. We have more then thousand HP-UX servers in the company plus some RedHat server. I am encountering the following two problems: 1) LDAP-UX has a bug. The defect number is JAGae32900. It fails to fail-over if LDAP-UX is running (funny stuff). Do you know if this bug was fixed? It seems to work only when ldap-ux bootups. I wouldn't like to build a cluster because of this bug. 2) I am trying to compile SSH using LpK patch. This patch allows to use a central repository (the ldap server) to distribute ssh-keys. Unfortunatel I am not able to compile. HEre is tha patch for OpenSSH: http://www.opendarwin.org/projects/openssh-lpk/ I have another question: where is library path set on hp-ux? I have seent that even if LPATH or LD_LIBRARYPATH are unset the system is able to locate the libraries on some position. Thanks Massimiliano Adamo |
| |||
| In article <1134429762.012512.164070@g44g2000cwa.googlegroups .com>, MaxAdamo wrote: > All, > > I am running a project to build an ldap server to be used for user > authnetication, for sudo administration and for SSH key management. > We have more then thousand HP-UX servers in the company plus some > RedHat server. > > I am encountering the following two problems: > > 1) LDAP-UX has a bug. The defect number is JAGae32900. It fails to > fail-over if LDAP-UX is running (funny stuff). Do you know if this bug > was fixed? It seems to work only when ldap-ux bootups. I wouldn't like > to build a cluster because of this bug. A simple google search shows that this defect was in version 3.00.0 of LDAP-UX. Since version 4.00.02 is now available, I would assume it has been fixed. I have used vesion 3.20 and 4.00.02 in an LDAP-cluster environment and failover seems to work fine.. > 2) I am trying to compile SSH using LpK patch. This patch allows to use > a central repository (the ldap server) to distribute ssh-keys. > Unfortunatel I am not able to compile. HEre is tha patch for OpenSSH: > http://www.opendarwin.org/projects/openssh-lpk/ No idea on that one... > I have another question: > where is library path set on hp-ux? I have seent that even if LPATH or > LD_LIBRARYPATH are unset the system is able to locate the libraries on > some position. Depends on the version of the OS you are using. Traditionally, that variable is SHLIB_PATH, but starting at (I think) 11.11, you can use either SHLIB_PATH or LD_LIBRARY_PATH. If you are asking how the variable is set, that depends on the shell. You can set a base value globally in /etc/profile (for bourne-ish shells) or /etc/csh.login (for csh-style shells). Kevin |
| ||||
| Kevin Collins wrote: > In article <1134429762.012512.164070@g44g2000cwa.googlegroups .com>, MaxAdamo > wrote: > > All, > > > > I am running a project to build an ldap server to be used for user > > authnetication, for sudo administration and for SSH key management. > > We have more then thousand HP-UX servers in the company plus some > > RedHat server. > > > > I am encountering the following two problems: > > > > 1) LDAP-UX has a bug. The defect number is JAGae32900. It fails to > > fail-over if LDAP-UX is running (funny stuff). Do you know if this bug > > was fixed? It seems to work only when ldap-ux bootups. I wouldn't like > > to build a cluster because of this bug. > > A simple google search shows that this defect was in version 3.00.0 of LDAP-UX. > Since version 4.00.02 is now available, I would assume it has been fixed. > > I have used vesion 3.20 and 4.00.02 in an LDAP-cluster environment and failover > seems to work fine.. mmhh .... take care. As far as I know versione 3.30 still has this bug. I have read all the documentation either for version and the problem is that this bug is not mentioned in the documents regard the version 4.0: it's not mentioned in the fixed bugs, is not mentioned in the still-open bug. Now seems to be a bug in the documentation -- Massimiliano |