> On Apr 10, 2015, at 7:46 PM, @lbutlr <[email protected]> wrote: > > Odd. I AM running it as a LaunchAgent.
Hmm, try changing the arguments to -DmS. That stops screen from forking in the background. launchd _really_ doesn't like that, and assumes the program has stopped running and unloads the daemon/agent (if it's not set to keep it alive). I wouldn't be surprised if it also kills anything else that belongs to the same process group. You may have to be an admin (or root) to see any messages from launchd. You can use sudo syslog -k Time ge -5m to see any and all output from the last 5 mins. If you are an admin, I dunno why it's not showing anything. You can try to load it up manually. launchctl load -w ~/Library/LaunchAgents/com.kreme.home.irssi.plist If screen isn't running after that, try launchctl start com.kreme.home.irssi It should be running after one of those. If it's not, try running launchctl list com.kreme.home.irssi - that should output a version of the plist that launchd has loaded. If it doesn't look like what you have, unload it and reload it. If you get an error, maybe try validating the plist file with plutil (though it looks fine to me). (Do note the output from launchctl list _daemon/agent_ isn't exactly in plist format, but it should look more or less the same.) ______________________________ Michael Nickerson _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
