Re: Plugins: proper way to change ld.so search path for a single binary

On Mon, 4 Sep 2000, Arthur Korn wrote: > Syslogd uses dlopen() to load the modules, thus ld.so has to > find the library for syslogd. Nope. An absolute path passed to dlopen() will work and cause the least security problems (on many systems, a group of users has wirte access to /usr/local/lib bec

Re: Plugins: proper way to change ld.so search path for a singlebinary

On Mon, 4 Sep 2000, Arthur Korn wrote: > Syslogd uses dlopen() to load the modules, thus ld.so has to > find the library for syslogd. Nope. An absolute path passed to dlopen() will work and cause the least security problems (on many systems, a group of users has wirte access to /usr/local/lib be

Plugins: proper way to change ld.so search path for a single binary

Hello. [ I'm not subscribed, please send me CCs ] I package modular syslog, and as the name implies, it uses modules for it's input and output methods. These modules are dynamic libraries, but since they are for exclusive use by msyslog, I'd rather have them in /lib/msyslog than in /lib, where I

Plugins: proper way to change ld.so search path for a single binary

Hello. [ I'm not subscribed, please send me CCs ] I package modular syslog, and as the name implies, it uses modules for it's input and output methods. These modules are dynamic libraries, but since they are for exclusive use by msyslog, I'd rather have them in /lib/msyslog than in /lib, where I