On Wed, 20 Sep 2000, Grin wrote:
> On Wed, Sep 20, 2000 at 01:56:10AM +0300, Igor Khasilev wrote:
>
> > ./configure --sbindir=/usr/local/sbin --sysconfdir=/usr/local/etc/oops
> > --localstatedir=/var/run --libdir=/usr/local/libexec/oops
> >
> > executables oops and oopsctl will be in /usr/local/sbin,
> > oops.cfg, tables, templates, rules will be in /usr/local/etc/oops,
> > oops.pid in /var/run,
> > modules in /usr/local/etc/oops,
> > in /usr/local/oops you will have directories logs/, storages/, DB/
>
> What about oopsctl pipe?
It goes to localstatedir, that is to /var/run in this case.
Hmm, this can be problem if oops-user can not write to /var/run...
>
> > Also can you help with one problem? This is how some users describe it. For
> > some reason Debian have old BerkeleyDB (ver 2.4.14) and newer version
> > (2.7.7) in distribution.
>
> The reason is the plenty of programs failing to work with 2.7.7, or at
> least compiled against the old version.
>
> > During ./configure procedure OLD vesion instead of
> > NEW version selected for some unknown reason. I have no Debian system to
> > test what happens. Can you send me paths to these libraries, so I can change
> > configure.in to solve this problem?
>
> He should remove old libdbXXX-dev and install new libdbXXX-dev package I think.
> Development files are always separated to -dev packages, and they can be
> installed independent of the shared library package's version.
And this is enough? Will configure detect which library it should link?
I think no.
>
> cya,
> grin
> =====================================================================
> If you would like to unsubscribe from this list send message to
> [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
> Archive is accessible on http://www.paco.net/oops/
>
Igor Khasilev |
PACO Links, [EMAIL PROTECTED] |
=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://www.paco.net/oops/
