[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
Here is a way (untested by me) to do what Andreas suggests: https://marek.dopiera.pl/2018/10/03/fetchmail-imap-idle-systemd- generators/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
Another suggestion would be to use systemd @service files, like the openvpn package does. You will get one daemon per vpn (in the openvpn case), and one per fetchmail config, if done properly. ** Changed in: fetchmail (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
** Changed in: fetchmail (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fetchmail (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
For a home system, e.g. mine, where I have 3 or 4 accounts to check
(more when the kids get older, of course), the FD limitiation is not
significant at all, and of course IDLE is far nicer than polling,
especially on servers which limit how often you can connect, but have no
objection to IDLE use. So, personally I'd see removing IDLE as a
backward step. (as far as I can see, none of the servers I connect to
support NOTIFY). NOTIFY would presumably not help across multiple
servers, either.
I really like fetchmail, but it struck me as annoying that the default
initscript would only start the one daemon. I.e. for my use I don't see
the bug as in the binary but in the initscript.
OK, a re-write of the codebase to make it capable of handling multiple
concurrent connections would also solve it (sounds challenging, but I
haven't looked at the source in years) and possibly use far less
resources on a big system. I'm not in a position to fund such a project,
sorry.
I felt my patch to the ubuntu/debian initscript a reasonable work-around
until someone was.
For checking sanity of the relvant config files, how about this extra
bit of shell script?
POLLING=`sed 's/#.*$//;/^\s*[Pp][Oo][Ll][Ll]\s/p;d' ${CONFIG} | wc -l `
IDLE=`sed 's/#.*$//;/^\s*[Ii][Dd][Ll][Ee]/p;d' ${CONFIG} | wc -l`
if test ${POLLING} -gt 1 -a ${IDLE} -gt 0
then
echo WARNING: ${CONFIG} uses the IDLE directive but tries to access ${POLLING}
accounts. Processing will not pass the first account with an IDLE unless there
is a problem with the connection.
fi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021699
Title:
fetchmail: IDLE - multiple daemons should be started
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
The limitation is documented, and I have always been considering killing the IDLE option upstream. Some server NOTIFY extension that is not as limited as IDLE is, might help, but I don't know how widespread that is. Else fetchmail would have to undergo internal restructuring and go on wasting sockets. For large POP toasters, you can't use IDLE anyways, on medium-sized, you might run out of file descriptors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
A suitable grep | wc pipeline could check and issue a warning, but the whole point of my patch is that at the moment there is no way to have more than one account if one of them is using IDLE. There is no problem with having multiple accounts per daemon (config file) if no IDLE is in use. If IDLE is used, then that connection will only terminate on a network error, and other accounts will not be queried more than once (depending on position in the file.) At the moment the sysadmin can 'lock up' their fetchmail daemon by adding the perfectly legal 'idle' annotation to one command. My patch does not stop this, but provides a mechanism to use it safely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
How do you make sure there is only one account per init script? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
** Attachment added: "replacement initscript" https://bugs.launchpad.net/bugs/1021699/+attachment/3214919/+files/fetchmail -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
