> On May 25, 2016, at 3:05 PM, Camden Narzt <camden.na...@hotmail.com> wrote: > > I’m sorry, I just assumed anyone doing any dev work on OSX would already run > homebrew.
I do lots of development work on OS X. I don't run homebrew. > > A much smaller test case with no installs so definitely a problem with > launchd/OS X is as follows: > > cat <<EOF > php.plist > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > <plist version="1.0"> > <dict> > <key>KeepAlive</key> > <dict> > <key>OtherJobEnabled</key> > <string>org.apache.httpd</string> > </dict> > <key>Label</key> > <string>php</string> > <key>ProgramArguments</key> > <array> > <string>/usr/bin/php</string> > <string>--server</string> > <string>127.0.0.1:9000</string> > </array> > </dict> > </plist> > EOF > sudo apachectl start > launchctl load php.plist > > Cam > > >> On May 25, 2016, at 3:23 PM, Axel Luttgens <axel.luttg...@skynet.be> wrote: >> >>> >>> Le 24 mai 2016 à 19:52, Camden Narzt a écrit : >>> >>> […] >>> >>> This is 100% reproducible on my MacBook Pro (Retina, 15-inch, Mid 2014) >>> running OS X 10.11.5 (15F34). >>> >>> Steps to reproduce (warning, this will almost certainly cause a kernel >>> panic): >>> >>> /usr/bin/ruby -e "$(curl -fsSL >>> https://raw.githubusercontent.com/Homebrew/install/master/install)" >>> brew install opentsdb >>> ln -s `brew --prefix hbase`/homebrew.mxcl.hbase.plist >>> ~/Library/LaunchAgents/ >>> ln -s `brew --prefix opentsdb`/homebrew.mxcl.opentsdb.plist >>> ~/Library/LaunchAgents/ >>> launchctl load ~/Library/LaunchAgents/homebrew.mxcl.hbase.plist >>> sleep 15 && launchctl load >>> ~/Library/LaunchAgents/homebrew.mxcl.opentsdb.plist >>> >>> >>> Note that running hbase via launchd and starting opentsdb manually does not >>> cause a kernel panic (or any other problems that I’ve noticed). >>> >>> Does anyone have any ideas about why this is happening? >> >> Hello Camden, >> >> Do you mean we have to download/install a lot of things for being able to >> answer your seemingly innocuous question "any ideas about why this is >> happening"? >> We all (well, at least me) on this list are now alarmed about a possible >> problem with launchd (or even Mac OS X), yet without any clue about that >> problem. >> Could you provide us with a case reduced to the bare minimum allowing to >> reproduce the problem you are encountering? >> >> >> TIA, >> Axel >> >> _______________________________________________ >> launchd-dev mailing list >> launchd-dev@lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/launchd-dev > > _______________________________________________ > launchd-dev mailing list > launchd-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/launchd-dev _______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/launchd-dev
