Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
This might not be the best place to ask this, but there doesn't seem to be a pecl_http mailing list or news group, so why not?
Have any of you used pecl_http successfully under apache? Whenever I install it on an Ubuntu server, restarting apache with /etc/init.d/apache2 reload fails. By fail I mean it gives an "[OK]", but if you do a ps -ef | grep apache you will see either no processes running, defunct processes, or only one process that refuses to die. If there is one process left you must kill it with a -s 9, then restart apache to get things going again (/etc/init.d/apache2 start).
If I force-reload it will work about 50% of the time. After I get it going, it will last a day or two, then crash. I've tried using both version 1.5.4 and 1.5.3, both with the same problem. If I re-compile the extension without cURL support, the problem goes away, but we need cURL support... any Ideas?
Just before the "crash" I get this in the log, as if someone did apachectl stop:
[Sun Aug 05 13:25:41 2007] [info] removed PID file /var/run/apache2.pid (pid=3686)
[Sun Aug 05 13:25:41 2007] [notice] caught SIGTERM, shutting down
Then one last apache2 service is running, which has to be killed -9 before apache can be restarted:
root 3686 1 0 Aug04 ? 00:00:01 /usr/sbin/apache2 -k start -DSSL
I've all but given up and have asked the developer to look at alternatives to using this package.