> I upgraded a FreeBSD 2.2.7 machine to 3.1, but left the samba binaries
> alone. Every thing still works. Then, I upgraded samba to 2.2.3 and
> complied it on the FreeBSD 3.1 machine. Now samba seems to run ok (no
> errors in samba logs) except logins do not work either from a
> win95 machine
> or directly using smbclient. The only error message is in the
> syslog as
> show below :
>
> smbd: no modules loaded for `samba' service
I'm pretty sure this is a PAM problem - FreeBSD 3.1 has PAM support, and the
standard Samba build spots it and chooses to use it, but seems to attempt to
use features that are not (yet?) implemented on FreeBSD's PAM. _A_ solution
is to compile Samba from the FreeBSD ports collection (though I haven't
noticed if the port has been updated to follow 2.0.3 yet). Another is to
simply track down the parts of the Samba build that detect PAM and hardwire
them to not find it.
It isn't an ELF issue anyway - I've had Samba V2 running on FreeBSD ELF
systems with no snags.
Cheers,
Dermot