scheduler core for timeout

[Marco Hernandez <marco@yukon.cren.org>]

Greetings:

	Scheduler seems to SIGBUS everytime a mail message times out
after three days ...  Below is a stack trace.

Core was generated by `/usr/local/mail/bin/scheduler -N64 -s'.
Program terminated with signal 10, Bus error.
procfs (find_procinfo):  Couldn't locate pid 0
|#0  0x1f3ec in expaux (vp=0x7dc78, index=26, 
    buf=0x2d83f8 "\rexpired after 3 days, problem was:\r500 (connect to mikespc.
optimal.com [199.35.230.9]: No route to host)") at update.c:497
497                 msgerror(vp, vp->cfp->offset[index], buf);
(gdb) bt
|#0  0x1f3ec in expaux (vp=0x7dc78, index=26, 
    buf=0x2d83f8 "\rexpired after 3 days, problem was:\r500 (connect to mikespc.
optimal.com [199.35.230.9]: No route to host)") at update.c:497
|#1  0x1f68c in expire (vp=0x7dc78, index=-1) at update.c:534
|#2  0x1a388 in reschedule (vp=0x7dc78, factor=0, index=-1) at agenda.c:105
|#3  0x1b8f4 in fifoschedule (wp=0x5aa58) at agenda.c:470
|#4  0x1ce34 in reclaim (fd=8) at transport.c:419
|#5  0x1d00c in waitandclose (fd=8) at transport.c:494
|#6  0x1dbb8 in readfrom (fd=8) at transport.c:817
|#7  0x1d4d8 in mux (quickcheck=0) at transport.c:604
|#8  0x14c48 in main (argc=3, argv=0xeffffefc) at scheduler.c:394

It is always the expire after 3 days message.  One thing is that 
appears is that index has a value of 26, so that offset[index], although
in scheduler.h it is defined as offset[1] if I rememeber correctly ???

Has anyone encountered this before ?  I'm not all that sure how index gets 
set and what it's significance is ...  

/Marco