[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google
  Web www.spinics.net

Re: Pam Perl or how to debug a pam module



It actually is the module writers guide that should be used. In terms of debugging once compiled as shown above, tools like nm, ldd and objdump can be used to verify library linking and function calls available within the compiled shared object.

Jason Gerfen


On Dec 21, 2011, at 2:59 PM, "ben" <ben@xxxxxxxxxxxxxxxxxx> wrote:

> On 12/20/2011 6:20 PM, Jason Gerfen wrote:
>> Linker errors? My first assumption is that you are trying to link to the PAM libraries, in which case...
>> 
>> gcc -o pam_module.so pam_module.c -llibpam 
>> 
>> Of course this is all listed within the developers handbook
>> 
>> Jas
> 
> That looks like it might be my problem. I will test tonight. could you
> point me to the developer's handbook, Which i assume is not the module
> writer's guide included with my distro.
> thanks,
> ben
> 
> -- 
> Ben Hildred
> Estimator
> Applied Plastic Coatings, Inc.
> 5000 Tabor St.
> Wheat Ridge, CO 80033
> 303 424 9200
> F: 303 424 8800
> ben@xxxxxxxxxxxxxxxxxx
> http://appliedplastic.com
> 
> _______________________________________________
> Pam-list mailing list
> Pam-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/pam-list

_______________________________________________
Pam-list mailing list
Pam-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/pam-list


[Fedora Users]     [Kernel]     [Red Hat Install]     [Linux for the blind]     [Gimp]

Add to Google Powered by Linux