I maintain an application that requires an aggregate method to run once daily.

As of right now it's running under a sudo-cron application and as such is tripped when the site is accessed. Since the script needs to be allowed to finish, the primary method it activates sets ignore_user_abort() to true and set_time_limit() to 0.

I may have been the cause since I've been checking in and out of svn all day, but despite this I had some data truncated during one of the runs. Most likely due to the script aborting, which it shouldn't be.

Therefore the question is raised, does ignore_user_abort() roll downhill? Any private methods run within the primary method should automatically be covered under the original ignore_user_abort() call should they not?

I'm going to avoid this whole fiasco in the next release by transferring it from the sudo-cron application to an asynchronous http request, but I'd still like to know for future reference.