[wp-trac] Re: [WordPress Trac] #4566: Cron Not Getting Called (fsockopen failing)

[WordPress Trac]

#4566: Cron Not Getting Called (fsockopen failing)
-----------------------------------+----------------------------------------
 Reporter:  chewblocka             |        Owner:  Nazgul  
     Type:  defect                 |       Status:  assigned
 Priority:  normal                 |    Milestone:  2.4     
Component:  Administration         |      Version:  2.2.1   
 Severity:  normal                 |   Resolution:          
 Keywords:  cron future has-patch  |  
-----------------------------------+----------------------------------------
Comment (by darkdragon):

 There isn't really another method for reliably calling the wp-cron.php
 without blocking execution. What I mean is that there isn't one for works
 both on PHP4 and PHP5. Well, besides cURL, but you count on it to be
 installed and enabled on all shared hosts.

 PHP5 does add several better ways, {{{file_put_contents()}}} along with
 streams to put the headers and nonblocking mode, would be a better method,
 but wouldn't solve the issue.

 As far as my research as bought up, there is no real nonblocking PHP
 execution, unless you use multitasking method. The only problem with the
 multitasking PHP methods, is that they are also unreliable.

 However, this doesn't correctly solve or have anything to do with the real
 problem.

 [b]Suggestion[/b]

 Don't use '@', just disable warnings. If fsockopen fails, you should do
 some other checks, however, some troubleshooters might want to get the
 warnings and you hinder those attempts.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/4566#comment:9>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software