Re: [monit] Compiling monit on Solaris9

[Andrew Ohnstad]

On Wed, Mar 26, 2008 at 8:24 AM, Jan-Henrik Haukeland <address@hidden> wrote:

On 26. mars. 2008, at 13.03, SMITH Duncan wrote:
> I get the following error:
>
> ld.so.1: monit: fatal: libssl.so.0.9.8: open failed: No such file or
> directory
> Killed
>
>

Looks like the runtime linker (ld) cannot find the ssl library. Its
been a long time since I used Solaris, but I believe you can export
this environment variable, so the dynamic linker will find the ssl
library.

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/ssl/lib

Or if Solaris has a ld configure file, such as /etc/ld.so.conf you can
add the ssl library there so you do not have to set the environment
variable mentioned above.


Ps. This means that other applications using ssl should get the same
error. Do they?

The problem analysis is correct, but the solution is not.

 

Solaris, since about Solaris 7 doesn't use LD_LIBRARY_PATH.  or ld.so.conf.  Instead there is a nifty command that totally manages libraries, and that magic is called 'crle'.

 

One should never, ever, ever set LD_LIBRARY_PATH on Solaris, or try to muck with any ld.so.conf type files (they usually don't even exist).

 

"crle" without any arguments will show you your current libraries paths.  To add a new one, first run crle to get the current path, then do:

 

"crle -l <original_paths>:<new_path>"

 

Note crle -l overwrites the existing path, so you must include all of the original paths, then tack on the new paths at the end, and the whole thing is colon delimited.

 

"crle -64" and "crle -64 -l" do the same magic for 64 bit libraries if you are using a compatable system.

 

Goooooooooooooooooooooogle for more info.