The default configuration for dansguardian is to log in /var/log/dansguardian, which isn't created by the RPM. Also, the default configuration runs as nobody.nobody, which means that /var/log/dansguardian, even if it existed, would have to be owned by user or group nobody. Generally speaking, the whole point of the user and group nobody is that they shouldn't have write access to anything. So I suspect that a user and group should be created for dansguardian in its %post script and that user and group should own /var/log/dansguardian.
Fixed in upcoming update.
dansguardian-2.10.1.1-3.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/dansguardian-2.10.1.1-3.fc11
dansguardian-2.10.1.1-3.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/dansguardian-2.10.1.1-3.fc10
dansguardian-2.10.1.1-3.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dansguardian'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-9919
dansguardian-2.10.1.1-3.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dansguardian'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9928
dansguardian-2.10.1.1-3.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
dansguardian-2.10.1.1-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.