Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Simple one really i'm sure. Just wondering if it is necessary to re-compile PHP everytime you want to add a new module or if using something like the --with-config-file-scan-dir=/usr/php.d/confs
Or whatever (obviously not that path. but you get the idea...). I'm basically wondering that to add a new module does it really need an php re-compile everytime or is it more that you can compile the module is some method ('shared' perhaps?) and then use the [modulename].ini with extesion=blah.so etc. So once apache restarted the module is usable. I'm thinking along the lines similar to how apache and DSO's work?
I'm hoping that makes sense... perhaps there is a better how to than the php installtion guide because that didn't seem to talk about this option at all, and did say that a recompile is nessasary everytime... i just wanted to check.
And to find out exactly what this is all about... --with-config-file-scan-dir=[blah]. Because otherwise it looks like something that will be just for adding the words extension=blha.so rather than just adding it into the php.ini file anyways.
Thanks for the reply... so i take it from that.. that you don't have to re-compile php to add another module in by using --with-[mod name]=[maybe a path to compiled module as well], everytime, and that its possible to:-
compile the module (as you would have to anyways) then if module was in an unusual place add that path to the ldconfig file and then just add the extension=asfsa.so into the php.in