[ic] email tag - large lists problem

Lyn St George lyn at zolotek.net
Tue Feb 9 11:36:10 UTC 2010

On Tuesday 09 February 2010 07:04:03 Rick Bragg wrote:
> This is all really great, and yet again shows the strength and
> flexibility of IC.  Same here, it is NOT SPAM, but for city alerts that
> people subscribe to.  Delivery time is somewhat critical, but deliver
> reliability and avoiding the browser from hanging is more important.
> Also, these "lists" need to be totally dynamically created, and
> managed.  
> One quick question about schedule_at, and child-process vs. a real
> mailing list like mailman;  Would any of these survive an interruption
> caused by a reboot?  Probably mailman or sendmail alias?
> Thanks!
> Rick

The child-process tag forks another instance of IC to run code specified by 
the tag immediately, so that would die in a reboot the same as the parent IC 

The schedule_at tag uses the at system to write an 'atjob' to the queue, 
normally in /var/spool/at/atjobs, and as this is a file it will survive a 
reboot - atjobs can be specified for months or years ahead if you want, or 
just the next minute after creation.  Reliability of the code to be executed 
is totally down to the code you write for the atjob to execute - as it's 
executed by the system it's no longer IC code but perl or shell scripting.


More information about the interchange-users mailing list