I'm trying to diagnose a boot-time problem, and it's made more difficult because the error messages are suppressed: May 21 18:38:48 localhost systemd-journal[127]: Suppressed 114 messages from /system/cloud-init.service The rate limit defaults of journald seem reasonable, but maybe they could be relaxed at boot time? (Either don't start counting until the system is up, or else have a much higher limit?)
We can certainly bump this limit, but I am pretty sure we shouldn't special case the boot part like this. Instead we should alter the burst limit generally.
How about keeping the numbers basically the same but increasing the interval? Currently, the default is 200 messages in 10 seconds; what if we change that to 1200 messages in 60 seconds?
I now changed the defaults to 1000 per 30s. Which is a bit higher than your values. I hope that makes sense. http://cgit.freedesktop.org/systemd/systemd/commit/?id=7f1ad696a273703789b624fe0b209fb63e953016
systemd-204-18.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/systemd-204-18.fc19
Package systemd-204-18.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-204-18.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23072/systemd-204-18.fc19 then log in and leave karma (feedback).
systemd-204-18.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.