Launchd, execve and execvp ...
On a fresh installation of Darwin 8.0.1, on a G4 Gigabit Ethernet, 1g RAM, 400MHz processor, I downloaded and installed the latest Macports and then did a selfupdate, which confirmed version 1.320. I then went to install AMP, which I did thusly: %sudo port install mysql4 +server %sudo port install apache2 +server %sudo port install php5 +mysql4 +apache2 +macosx During these installations I encountered the previously documented ftp bug. At these points, I stopped the installation, deleted the temp file, manually ftp'd the file into the correct directory and then restarted installation. After these three items installed successfully, I rebooted the machine. I got these error messages before the login prompt:
launchd: org.mapcports.mysql4: execve(): No such file or directory launchd: org.mapcports.mysql4: execvp(~/opt/local/bin/daemondo",...): No such file or directory launchd: org.mapcports.apache2: execvp(~/opt/local/bin/daemondo",...): No such file or directory launchd: org.mapcports.apache2: execve(): No such file or directory
Upon logging in, I ran
launchctl load -w /Library/LaunchDaemons/org.macports.mysql4.plist
and received this error
launchd: org.mapcports.mysql4.plist: execve(): No such file or directory
similarly, I ran
launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist
and got
launchd: org.mapcports.apache2.plist: execve(): No such file or directory
I've Googled looking for a fix and can't seem to find one and have searched the two months of archives of this list, also finding nothing similar. Any thoughts on this problem would be appreciated. TIA. \dmc -- *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ David M. Cole dmc@colegroup.com Editor & Publisher: The Cole Papers; NEWSINC. V: (650) 557-9595 Consultant: The Cole Group <http://colegroup.com/> F: (650) 475-8479 *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
On Oct 29, 2006, at 12:18, David M. Cole wrote:
On a fresh installation of Darwin 8.0.1, on a G4 Gigabit Ethernet, 1g RAM, 400MHz processor, I downloaded and installed the latest Macports and then did a selfupdate, which confirmed version 1.320.
Wait, are you using Mac OS X, or just Darwin? I thought part of the reason for renaming DarwinPorts to MacPorts was that we didn't want to support plain Darwin anymore....
At 1:54 PM -0600 10/29/06, Ryan Schmidt wrote:
Wait, are you using Mac OS X, or just Darwin? I thought part of the reason for renaming DarwinPorts to MacPorts was that we didn't want to support plain Darwin anymore....
yes, just plain darwin ... din't know about that restriction (you might want to put that on a web page or something ...). \dmc -- *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ David M. Cole dmc@colegroup.com Editor & Publisher: The Cole Papers; NEWSINC. V: (650) 557-9595 Consultant: The Cole Group <http://colegroup.com/> F: (650) 475-8479 *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
On Oct 29, 2006, at 13:09, David M. Cole wrote:
At 1:54 PM -0600 10/29/06, Ryan Schmidt wrote:
Wait, are you using Mac OS X, or just Darwin? I thought part of the reason for renaming DarwinPorts to MacPorts was that we didn't want to support plain Darwin anymore....
yes, just plain darwin ... din't know about that restriction (you might want to put that on a web page or something ...).
Oh, there are lots of things we should put on the web page or something. This transition we're currently undergoing has thrown everything into disarray. I believe the problem was that most of the developers did not in fact have a pure Darwin box to test with, so things constantly broke for Darwin, and with Macs and therefore Mac OS X gaining popularity, it was felt that supporting Darwin was not very feasible. I have the apache2 port installed and I do use launchctl to start and stop it, and it works fine on Mac OS X. But I also unfortunately have no experience with pure Darwin.
On Oct 29, 2006, at 3:31 PM, Ryan Schmidt wrote:
On Oct 29, 2006, at 13:09, David M. Cole wrote:
At 1:54 PM -0600 10/29/06, Ryan Schmidt wrote:
Wait, are you using Mac OS X, or just Darwin? I thought part of the reason for renaming DarwinPorts to MacPorts was that we didn't want to support plain Darwin anymore....
yes, just plain darwin ... din't know about that restriction (you might want to put that on a web page or something ...).
Oh, there are lots of things we should put on the web page or something. This transition we're currently undergoing has thrown everything into disarray.
I believe the problem was that most of the developers did not in fact have a pure Darwin box to test with, so things constantly broke for Darwin,
This is true, but most ports should work with plain Darwin. If things are broken, patches are always welcome.
and with Macs and therefore Mac OS X gaining popularity, it was felt that supporting Darwin was not very feasible. I have the apache2 port installed and I do use launchctl to start and stop it, and it works fine on Mac OS X. But I also unfortunately have no experience with pure Darwin.
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
participants (3)
-
Daniel J. Luke
-
David M. Cole
-
Ryan Schmidt