hi all

the reboot and halt scripts stop when trying to unmount the /usr partition. 
the script is terminated and the system does not reboot or halt properly. 
very nasty...

a "fuser -vm /usr" command at this point shows the following:
                     USER        PID ACCESS COMMAND
/usr                 root        8471 ....m.  S01REBOOT

this means, that a shared library is in use by the rc script itself. i 
discovered, that the use of nss_ldap is the reason for this. tell the system 
in /etc/nsswitch.conf to use ldap and this phenomenon happens. i also 
discovered that when the whole filesystem is in one partition, it does NOT 
happen. it only happens when /usr is on a separate partition (usually on 
servers).

doing a "ldd /lib/libnss_ldap-2.2.5.so" shows the following:
        libldap.so.2 => /usr/lib/libldap.so.2 (0x40024000)
        liblber.so.2 => /usr/lib/liblber.so.2 (0x40055000)
        libsasl.so.7 => /usr/lib/libsasl.so.7 (0x40061000)
        libkrb4.so.2 => /usr/lib/libkrb4.so.2 (0x4006f000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x40084000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x400e6000)
        libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x400f7000)
        libssl.so.0 => /usr/lib/libssl.so.0 (0x400fb000)
        libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0x4012c000)
        libdb-3.3.so => /lib/libdb-3.3.so (0x401f6000)
        libdl.so.2 => /lib/libdl.so.2 (0x40295000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x40298000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x402ac000)
        libc.so.6 => /lib/i686/libc.so.6 (0x402bd000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x403dd000)
        libpam.so.0 => /lib/libpam.so.0 (0x4040b000)
        libdes425.so.3 => /usr/lib/libdes425.so.3 (0x40413000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

as you can see there are several libraries loaded by lib_nssldap that reside 
on /usr/lib. copying these to /lib resolves the problem.

many of the postings here regard desktop programs in mandrake linux. i 
understand, that this is important to mandrake. but wouldn't it be nice to 
play an important role in the server market? this is not the only issue when 
using ldap with mandrake (see my other postings on this list). i hope, 
mandrake will fix these bugs as soon as possible.

these problems were not difficult to find (why did nobody at mandrake test 
this? i think the beta tests are no good for such features because most of 
the freaks out there only test their video players etc.)

ldap is important when trying to replace windows servers with linux/samba and 
manage user accounts. try to improve quality please...

thank you
spiderboy

Reply via email to