|
It will log to security (also to tty0 or the first text terminal at the
workstation). You can compile it with -DDEBUG as well as putting the
#define in the source code. Since you are working with a fresh RedHat,
the package should put everything in the perfect spot (Source Forge
source is best, which is more than likely what you are doing). So, with it NOT putting anything in syslog, you might want to check the source. One thing I found is that there are no wrappers for DEBUG, but there is the D(()) macro. Plus, there should be a function called "askForPassword", which I can't find in the current SF version of it. I might suggest looking at the code and ensuring that there is plenty of "#if DEBUG" lines. Joe firstcon wrote: Hi Joe, thanks for your reply. The box has been installed yesterday, with a clean fresh RH9 :) There is no other pam_mysql around except the one in /lib/security i just compiled before from pam_mysql-0.5.0 i got from sf.net I did some more tests: pam_mysql.c assumes that the mysqlserver is on localhost, because in mysql_real_connect() the port-number is hardcoded to 0. I already tried to change that to 3306, for example. But it still doesn't work. The problem is that i really have compiled with: #define DEBUG but i don't see any messages in syslog. To which syslog facility would it be logged? I assume it should either go to messages or secure logfile. Nothing in both of them. Did you ever connect to a remote mysqlserver with pam_mysql? I can connect to local mysqlserver, but every attempt to connect to a remote mysqlserver fails - without any messages in syslog. Just to be sure: yes, the remote mysqlserver is open for my client machine, i can use the mysql client to connect to it. Kind regards, Andy Original Message, Date 04.03.2004, 23:59 h: JL> I think Andy's just authenticating against MySQL (something I do on some JL> of the test boxes I play with). JL> Andy: I would first ensure that the application is authenticating using JL> the proper module (i.e. first check that there aren't multiple JL> pam_mysql.so modules around and that the module is "getting installed" JL> to the wrong place). You may very well have a module that is configured JL> for using debug, but just doesn't get loaded. JL> Joe JL> Aaron Konstam wrote: |
