tags 380459 + pending confirmed thanks Hello Riccardo, * Riccardo Stagni <[EMAIL PROTECTED]> [2006-07-31 19:48]: > On Mon, Jul 31, 2006 at 01:30:40PM +0200, Nico Golde wrote: > > I thought about your solutions but here comes mine :) > > From fetchmail(1): > > Normally, calling fetchmail with a daemon in the background sends a > > wake-up signal to the dae- > > mon, forcing it to poll mailservers immediately. (The wake-up signal is > > SIGHUP if fetchmail is > > running as root, SIGUSR1 otherwise.) The wake-up action also clears any > > 'wedged' flags indi- > > cating that connections have wedged due to failed authentication or > > multiple timeouts. > > > > So my fix here is to get the pid from the pid-file and send SIGUP (kill -1) > > to the > > process. Works pretty well and imho is the sanest solution here. > > What do you think? > Very smarter! :)
Ok after discussing the issue with upstream I decided to take your initial method because fetchmail is able to decide itself how to deal with a wake-up when called correctly. Also if I like the signal based method alot more. > I read the manpage a lot of times, but I ever found nothing, perhaps > because I was looking for awake: > man fetchmail > /awake > Pattern not found (press RETURN) > "mmmh... It isn't awakenable by hand??? queer..." > :) Yes I also had the problem, upstream did some work do make it easier :) > Just another question: why there are two pid in the pidfile? If I stop the > daemon it correctly removes /var/run/fetchmail/fetchmail.pid, but when I > restart it writes two numbers: the right pid (first row) and 300 (second > row, that doesn't correspond to any process). The second number is the sleep interval. Anyway, fix will be included in the next upload, thanks for your very good report! Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://nion.modprobe.de/blog/ Forget about that mouse with 3/4/5 buttons - gimme a keyboard with 103/104/105 keys!
pgpFwSz2NUqi6.pgp
Description: PGP signature
