> Le 26 mai 2016 à 00:05, Camden Narzt a écrit : > > I’m sorry, I just assumed anyone doing any dev work on OSX would already 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
Hello Camden, Thanks for sharing. So, I guess the morality is "currently, don’t even try to make use of the OtherJobEnabled key"? Thanks again, Axel _______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/launchd-dev
