You should attach the problematic launchd.plist to that Radar.
-damien
> On 24 May, 2016, at 16:07, Camden Narzt wrote:
>
> Radar:26456448
>
> Camden
>
>> On May 24, 2016, at 1:10 PM, Kevin Elliott wrote:
>>
>>
>>> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! wrote:
>>>
>>>
>>> On 24
Radar:26456448
Camden
> On May 24, 2016, at 1:10 PM, Kevin Elliott wrote:
>
>
>> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! wrote:
>>
>>
>> On 24 May 2016, at 18:52, Camden Narzt wrote:
>>
>>> Does anyone have any ideas about why this is happening?
>>
>> The answer to the question “
> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! wrote:
>
>
> On 24 May 2016, at 18:52, Camden Narzt wrote:
>
>> Does anyone have any ideas about why this is happening?
>
> The answer to the question “Why does my system kernel panic?” is pretty much
> always “Because of a bug in the OS?”
On 24 May 2016, at 18:52, Camden Narzt wrote:
> Does anyone have any ideas about why this is happening?
The answer to the question “Why does my system kernel panic?” is pretty much
always “Because of a bug in the OS?” The system is not supposed to panic
unless you do obviously dodgy things (
I was pointed at this mailing list to try and figure out what seems to be a
pretty bad launchd bug.
I recently added an opentsdb formula to homebrew, including a launchd plist.
However when I load the plist with launchctl load
~/Library/LaunchAgents/homebrew.mxcl.opentsdb.plist my system hangs,
