I tested on our server with a logrotate whose "copytruncate" is replaced
with "nocreate". It work as expected: file is moved and not re-created,
thus carbon detect the logrotate and write to new log file (without a
bunch of NUL ascii character).
I attached the new debdiff with the "copytruncate" replaced with "nocreate".
diff -Nru graphite-carbon-0.9.12/debian/changelog
graphite-carbon-0.9.12/debian/changelog
--- graphite-carbon-0.9.12/debian/changelog 2014-01-13 22:44:07.000000000
+0100
+++ graphite-carbon-0.9.12/debian/changelog 2014-01-14 16:17:54.000000000
+0100
@@ -1,3 +1,9 @@
+graphite-carbon (0.9.12-2.1) unstable; urgency=medium
+
+ * replaced "copytruncate" with "nocreate" in logrotate (Closes: #733856)
+
+ -- Pierre Fersing <pier...@pierref.org> Tue, 14 Jan 2014 16:14:47 +0100
+
graphite-carbon (0.9.12-2) unstable; urgency=medium
* added systemd service file: carbon-cache.service
diff -Nru graphite-carbon-0.9.12/debian/graphite-carbon.logrotate
graphite-carbon-0.9.12/debian/graphite-carbon.logrotate
--- graphite-carbon-0.9.12/debian/graphite-carbon.logrotate 2014-01-13
22:44:07.000000000 +0100
+++ graphite-carbon-0.9.12/debian/graphite-carbon.logrotate 2014-01-14
16:14:43.000000000 +0100
@@ -6,5 +6,5 @@
delaycompress
notifempty
sharedscripts
- copytruncate
+ nocreate
}
