Project

General

Profile

Actions

Bug #4739

closed

growl notifications cause excessive delays when configured with non-resolvable hostname

Added by Chris Buechler over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Notifications
Target version:
Start date:
06/02/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

When growl notifications are configured to go to a hostname, and that hostname doesn't resolve, it causes a 1 minute delay in notify_via_growl(), from the fsockopen in growl.class taking that long to timeout. The timeout parameter to fsockopen doesn't apply to its DNS queries, so doesn't help there.

Actions #1

Updated by Chris Buechler over 6 years ago

  • Status changed from New to Feedback

pushed a change that takes the delay down from 1 minute to about 20 seconds, which is probably about the best we can do without causing unnecessary failures.

Actions #2

Updated by Chris Buechler over 6 years ago

  • Status changed from Feedback to Resolved

fixed

Actions

Also available in: Atom PDF