Bug 6303 - swat fails to find libraries
Summary: swat fails to find libraries
Alias: None
Product: Samba 3.2
Classification: Unclassified
Component: SWAT (show other bugs)
Version: 3.2.11
Hardware: SGI IRIX
: P3 major
Target Milestone: ---
Assignee: Björn Jacke
QA Contact: Samba QA Contact
Depends on:
Reported: 2009-04-29 16:54 UTC by Jim Brown
Modified: 2009-07-15 11:44 UTC (History)
0 users

See Also:

Wrapper for inetd (330 bytes, text/plain)
2009-04-29 16:56 UTC, Jim Brown
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Brown 2009-04-29 16:54:41 UTC
system: IRIX 6.5.30; samba 3.2.11

swat does not find samba libraries when run by inetd.
I wrote a wrapper for inetd to call so the libraries are found.
Comment 1 Jim Brown 2009-04-29 16:56:43 UTC
Created attachment 4091 [details]
Wrapper for inetd

This wrapper allows inetd to run swat on IRIX.
I put it in samba/sbin as swat.sh and call it from inetd.conf.
Comment 2 Jim Brown 2009-04-29 16:58:11 UTC
I will re-test with 3.3.4 (building now) to see if it has the same problem.
Comment 3 Jim Brown 2009-05-11 08:09:07 UTC
I see the same problem with 3.3.4.
Comment 4 Björn Jacke 2009-07-15 11:09:56 UTC
You should either install the libraries somewhere, where your library search patch points to. If you don't do that you have to work around it like you did with your wrapper script.
Comment 5 Jim Brown 2009-07-15 11:20:16 UTC
I'd like a pony too.

The libraries are located in /usr/samba/lib.
They are not installed in a system directory searched by the loader (unless they are explicitly added to the library search path).

Swat is run by inetd.  I do not want to expose the samba libraries to every system program just so the loader can find them when inetd starts swat.

The samba start/stop script has the same library problem and requires the same work around.

How am I supposed to solve this problem on an IRIX system without a wrapper (e.g. swat.sh)?  Explicitly copying the samba libraries to a system library area is pretty lame (even symlinking them).
Comment 6 Björn Jacke 2009-07-15 11:44:11 UTC
this won't be fixed any better. extend your library search path, insall the libs in your systems's lib paths or tell configure not to use shared libs if you dislike the first options.