Project

General

Profile

Bug #4739

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

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

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

0%

Estimated time:
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.

Associated revisions

Revision dbd919ec (diff)
Added by Chris Buechler over 4 years ago

Don't call growl if the configured address isn't an IP or resolvable
hostname. Avoids 1 minute timeout delay in fsockopen in growl.class. Cuts
that down to about a 20 second timeout. Ticket #4739

Revision b532745a (diff)
Added by Chris Buechler over 4 years ago

Don't call growl if the configured address isn't an IP or resolvable
hostname. Avoids 1 minute timeout delay in fsockopen in growl.class. Cuts
that down to about a 20 second timeout. Ticket #4739

Conflicts:
etc/inc/notices.inc

History

#1 Updated by Chris Buechler over 4 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.

#2 Updated by Chris Buechler over 4 years ago

  • Status changed from Feedback to Resolved

fixed

Also available in: Atom PDF