Why are you specifying --with-authshadow with --with-authpam? PAM can authenticate shadow password users and normal password users. I'm guessing that the authdaemon was authenticating to the shadowpassword file and not with PAM (check your syslog entries, if it's authenticating via PAM, there will be entries indicating such) Try compiling with only --with-authpam and see if that fixes your problem. Cheers, Tren. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - Tren Blackburn - Owner mailto:[EMAIL PROTECTED] = = End of Time Networks http://www.theendoftime.net - - (403) 269-2122 = =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- On Thu, 1 Feb 2001, Andy Bradford wrote: > Ok, > I finally seem to have it working properly, however, it was due to > something that I didn't expect. I have another system on which it has > been working properly for some time now so I decided to check out the > ./configure options that I used for it. Here is the one that works. > > ./configure --without-authmysql --without-authldap --with-authshadow --with-authpwd >--with-authpam --with-authuserdb --with-cachedir=/var/cache/sqwebmail --enable-https >--enable-hardtimeout=14400 --enable-softtimeout=7200 >--enable-cgibindir=/home/httpd/cgi-bin --with-maxformargsize=1024000 > > And here is the one that doesn't. > > ./configure --enable-https --enable-webpass=yes --enable-maxpurge=90 --with-authpam >--with-authshadow > > Now, I know it's not the cachedir, https, webpass, hardtimeout, > softtimeout, cgibindir or maxformargsize that are causing the problem. > So, why do I have to specifically disable authmysql and authldap for it > to run with authpam even though I specifically indicated to include > authpam? Is this just something that *must* be done for it to work > properly? If so, it isn't documented. Anyway, now that I know where > the problem is I can take care of it. Thanks for the ears. :-) > > Andy > >
