No delay when connected, but the delay can be upwards of a few minutes, when it is not connected.
Here is what I've checked so far: Strace reports waitpid(-1, 0xbfffff8c, WNOHANG) and waits on this for a while, and keeps doing this over and over. I checked the sources, and it seems that exim4 starts up threads, waits for them, and times out over and over when the threads can't connect to the interface (src/daemon.c). I believe the threads are supposed to connect to the smtp server, and when they can't (due to a disconnected cable), they die, and then the main thread just waits for them until it times out. What I tried to do was to disable the interface, and start up exim, and then reenable the interface. What I get is a quick start of exim, but it then refuses to send mail b/c it claims that the smtp server is unreachable. I read that in the log. What I feel like I need to do is make a cron script that tries to ping the server, and only once that pings should I start the MTA. But I was hoping there was some other way to get around this. Nachum -----Original Message----- From: Josh Zlatin-Amishav [mailto:[EMAIL PROTECTED] Sent: Thursday, May 20, 2004 10:52 AM To: Nachum Kanovsky Subject: RE: Debian with Exim4 On Thu, 20 May 2004, Nachum Kanovsky wrote: > I can't always boot with the network up, but the loopback is up, what > can I do to stop this network delay??? And what exactly is it waiting > for? It should not be a timeout on dns, b/c both entries are in the > hosts file? And why else would exim be trying to access the network? Nachum, How long is the delay when the machine is connected to the network? -- - Josh GPG: F5A7 6196 13B5 270F B578 221F 80D1 99C8 4AC6 8C29 ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
