apache2 launchd plist bug?
ryandesign at macports.org
Tue Mar 27 22:47:12 PDT 2007
On Mar 27, 2007, at 22:55, Karl Timmermann wrote:
> I'm new to this list but was hoping someone could help me. I
> recently installed MacPorts 1.4 RC2 and compiled from source. Once
> installed, I did a port file update, etc before installing apache2
> + php5 + mysql5. Everything went pretty smoothly (except for some
> app named conftest that crashed - see crash report below - I'm not
> sure it matters.)
I get that too, when compiling gettext on Core 2 Duo MacBook Pro. I
wish it wouldn't do that. It has nothing to do with MacPorts; it also
happens when compiling gettext outside of MacPorts. I hadn't gotten
around to reporting it to the gettext developers yet. If you would
like to do so, please do.
> So then I followed instructions to copy over a default httpd.conf
> file, along with a default php.ini file
> and then created the launchd startup item by copying the plist and
> loading it in.
What do you mean? What did you copy? From where? Installing apache2
should have created the org.macports.apache2.plist launchd item for
you. Installing mysql5 +server (which I notice you didn't mention)
should have created the org.macports.mysql5.plist launchd item for you.
> When I restarted, apache2 starts as expected and I can access my
> webserver. So far so good.
> The problem is that after a while - maybe about an hour of use,
> every application in OS X starts to die - I get the spinning
> rainbow of death. Force quitting works, but other apps keep dying,
> even apps I restart. Even the Finder dies. So I force a reboot and
> it works for about 2 minutes, and then does the same thing again.
> To fix this problem, I boot into single user mode and delete the
> 'org.macports.apache2.plist' file and reboot. Everything then goes
> back to normal.
> I then test to make sure it was that plist file by installing the
> port again, and same problem shows up again. Any ideas? I'm running
> on a MacBook Pro (Intel Core 2 Duo).
That's not good. I've never seen such behavior before.
More information about the macports-users