thanks for the reply. that's what i made until now. but what i tried (without success) was attach the process to gdb and try to follow it. for example starting xdm in gdb and locating the problem in pam (without using the logs on stderr) and backtracing it. that means it's impossible debug it with gdb since user changes new process executions are made. regards, m96. On Fri, 2002-03-29 at 14:25, Jenn Vesperman wrote: > On Fri, 2002-03-29 at 21:56, m96 wrote: > > hi, > > > > as a novice c & gdb programmer & user, i just wanted to ask if anyone > > knows a way if there is a way to debug a pam module. i guess it should > > be possible but until now i had no success. > > In /etc/pam.d/(service name of the application), edit the line > with the module you're after. Add 'debug' to the end of that line. > The debug information will be sent to the syslog. > > EG: > > # > # /etc/pam.d/login > # > > auth required pam_unix.so debug > > > > If that doesn't give enough detail, you can install the module source > and hack away. > > > > > Jenn V. > -- > "Do you ever wonder if there's a whole section of geek culture > you miss out on by being a geek?" - Dancer. > > jenn@anthill.echidna.id.au http://anthill.echidna.id.au/~jenn/ > > > > > _______________________________________________ > > Pam-list@redhat.com > https://listman.redhat.com/mailman/listinfo/pam-list >
