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
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
Server Team, which is subscribed to fetchmail in Ubuntu.
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
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
Server Team, which is subscribed to fetchmail in Ubuntu.
https://bugs.launchpad.net/bugs/1021699
Title:
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
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
