From: Matthias A. <mat...@gm...> - 2006-11-22 01:35:37
|
"Roberto Meyer" <rob...@gm...> writes: > I'm still havin trouble with it. I'm running fetchmail from user's cron. > > Even if it's a network problem, I expect fetchmail to die after a > while. But sometimes it doesn't happen. > > I've modified the default 600 seconds fetchmail should wait for any > server response to 60 seconds but it still hangs in my process list. Do you have daemon mode enabled? Else see Jakob's reply. > Example pasted (process stopped at 2pm, I found it at 5pm, which means > 3 hours without downloading mail!) How do you "stop" the process? Did you kill fetchmail or just the /bin/sh wrapper? And if it's "someuser"'s process, how can you be sure it's not been restarted by cron in the meanwhile? > Any idea of why is this happening? I'm running fetchmail release > 6.2.5+NTLM+SDPS+SSL+NLS over Debian Sarge. Even though I consider 6.2.X obsolete and won't fix any bit in it unless someone tosses $$,$$$.$$ my way, that's not a known failure mode for fetchmail 6.2.X either. So: what did you do? what did you get? what did you want instead? -- Matthias Andree |