[DGD] Call_out question

[Felix A. Croes]

Noah Lee Gibbs <angelbob at monkeyspeak.com> wrote:

>   This just keeps getting weirder.  I've put a DRIVER->message() call into 
> the Kernel Library's _F_callout() function.  I tested it and it does, in 
> fact, give a message on every call_out.  Fine.  I put a DRIVER->message() 
> at the end of initd.c's create() function so I know it's going off the end 
> of that.
>   I put log messages in to make sure I'm scheduling call_outs 
> successfully.  I am.  Weirdly, DRIVER->message() isn't showing up, but my 
> LOGD->write_syslog() call is happening just fine, so I know I'm scheduling 
> both call_outs, and they both(!) have a call_out handle of 1.  Shouldn't 
> they be different from each other?  I'm pretty sure they're both active 
> at once.
>   But it turns out that it *is* accepting telnet connections eventually...  
> It's just that there's a *very* long delay before that happens, and before 
> any of the call_outs happen.  But only if I schedule the call_outs.


Anything like this?
  
 - Fixed a spurious pause that would occur if the first callout started after a
   cold boot had a delay of 0. 
	  
That's from the Changelog -- fixed in version 1.34.  Which version of
DGD are you using?
	     
Regards,
Dworkin
_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd