OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: adrien mistretta (adrien.mistrettat-online.fr)
Date: Tue Sep 25 2001 - 12:02:33 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    > Thanks for the update. So my first guess was right: Solaris was
    > hosed. A broken lock daemon can really cripple a system, even though
    > sending a file descriptor does not directly involve lock daemons.
    >
    > How did you figure this one out?
    >
    > Wietse

    By chance we had several box running which approximately the same
    configuration, and only one of them got the problem, so we did a diff between
    the filesystems. A lot of non-vital configuration files are centralised on a
    cachefs filesystem and there is some links pointing on them.
    unfortunately on the broken box, /etc/services pointed to
    /cachefsmount/etc/services instead of being local, so at boot time, lockd did
    find what he expected.
    As always this is a stupid error :)

    Adrien
    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users