Diogenes S. Jesus
Diogenes S. Jesus
@tim-seoss you may want to take a look on [ACME-DNS](https://github.com/joohoi/acme-dns)
@bmw I think people could live with creating and distributing third-party plugins without the need to have them PR'ed into certbot. My only current problem is: third-party plugins are second-class...
@bmw First, sorry for the rant-like post. But I think I was not very clear on this. Yes, cosmetically speaking that could be improved. But the matter of fact is...
@bmw TL;DR this issue should be reopened https://github.com/certbot/certbot/issues/6040
@bmw upon further inspection you're right, this is not related to #6040 - but to #4351. I particularly liked the suggestion [here](https://github.com/certbot/certbot/issues/1549#issuecomment-166894540): In order to avoid the limitations of #4351...
I can confirm this is still an issue - I was bulk importing from a NFS and after rebooting / remount files which were already processed were being again processed...
I think we can close this - [read more](https://github.com/logstash-plugins/logstash-input-file/pull/50#issuecomment-151438118).
+1 !! :) this is particularly painful in a bulk import. Is there any workaround suggested? maybe by monitoring the folder for new files and spawning one logstash-forwarder per file...
By the way, what's the suggested workaround here? logstash-forwarder doesn't also multithread as expected. Even if it does, after forwarding it to log stash the input-lumberjack plugin doesn't support multithreading....