Subject: Re: Modules not loading with asun2.1.4pre39
From: Rob Bos (rbos@sandwich.net)
Date: Tue Nov 07 2000 - 17:16:30 EST
Okay.. I'm having the prezact same problem as described in this message
several months ago - only those two modules will load, and none else will. I'm
running with shadow passwords enabled, PAM disabled, on netatalk-1.4.99. -
otherwise, it's a default installation.
Exhausting the archives of this maillist pretty thoroughly didn't pull up any
answers to this problem, I'm hoping that jeff managed to solve it.
Either way, can I get suggestions?
Rob Bos
On Tue, 6 Jun 2000 Dejan Muhamedagic wrote:
> Hi,
>
> On Mon, Jun 05, 2000 at 09:08:09PM +0000, jeff b wrote:
> > For one reason or another, none of my UAMs will load, with the exceptions
> > of uams_randnum.so and uams_guest.so
> >
> > All uams in the directory were specified (with one exception, in each
> > case), and yet only those two modules were loaded.
>
> Do you mean specified in the startup file as arguments to afpd?
> Are you definitely sure that this is the case? Because, if an UAM
> can't be loaded then an error message should be issued. You
> should be able to see how afpd was started by using 'ps auxw |
> grep afpd' and looking at the process which is running as root.
> Or trace (set -x) the startup script.
>
> If UAMs are specified on the line, don't load and there are no
> error messages than I'm in a complete dark.
The UAMs were specified in the netatalk.conf script (which is passed as -U
[modules]) and also in the
afpd configuration file. They don't load.
I have only been checking /var/log/messages for errors, of which there are
none.
I ldd'd the modules, and it turns out that uams_randnum.so and uams_guest.so
(the two modules that work)
are for some reason statically
linked. Any idea why they are, or why this could be causing problems? Even the
cleartext modules aren't
working. I didn't see anything in the
etc/uams/Makefile to indicate static compilation of specific modules...
--
Rob Bos, rbos@{sandwich.net,linux.com}, part of the vanguard into the future
Our OS who art in CPU, UNIX be thy name.
Thy programs run, thy syscalls done,
In kernel as it is in user!
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:35 EST