My Oracle Support Banner

Imapd Resists Using A Wrapper To Invoke An Interpose Library (Doc ID 2638342.1)

Last updated on FEBRUARY 20, 2020

Applies to:

Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.


Imapd resists using a wrapper to invoke an interpose library.

An interpose library was provided to address an mmap() bottleneck issue.

It appears that the Solaris dynamic loader goes out of its way to prevent using preload libraries if root is not the running user.
RBAC was set so stop/start of the application could be performed as the application user, without needing to be root.

A wrapper like the following was created:

Unfortunately, the following occurred:

$ stop-msg imap
Connecting to watcher ...
imap server is not running

...because it tells watcher the name of the binary:

$ /opt/sun/comms/messaging64/lib/msstart -l 2>&1 | grep imap
imapd-orig: 3099

Could there be some incredibly simple solution or workaround to this issue?

Is there any anticipated problem with copying imapd to a different location and having the wrapper script run that way?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.