Description of problem:
After the logrotate job runs for sigul, the sigul log files show no further activity despite sigul continuing to run fine otherwise.

Version-Release number of selected component (if applicable):
sigul-0.100-4.fc21.noarch

How reproducible:
always

Steps to Reproduce:
1. configure a working sigul environment
2. tail -F /var/log/sigul_{bridge,server}.log
3. either wait for the weekly logrotate job to come around or manually trigger it

Actual results:
Both the sigul_bridge.log and the sigul_server.log go silent once logrotate runs.

Expected results:
Logging should continue as it did before logrotate executed.

Additional info:
I successfully used the following patch to remedy the problem for both the bridge and server components.

--- /etc/logrotate.d/sigul.orig 2014-06-08 07:53:25.000000000 -0400
+++ /etc/logrotate.d/sigul      2015-05-19 09:36:32.184033456 -0400
@@ -1,4 +1,5 @@
 /var/log/sigul*.log {
        missingok
        notifempty
+    copytruncate
 }


This approach does leave a very small window where logged content may be lost while logrotate runs, but that's drastically better than the current behavior where all content is lost after logrotate runs.