Properly document new backlog file resilience

[inn-innduct.git] / backends / innduct.c

diff --git a/backends/innduct.c b/backends/innduct.c
index 57eb9dba3e99e11b76ad94f4e19c8285038dfad3..092c69356ad5f838e5a0ffa1067ab4224436dcb5 100644 (file)
--- a/backends/innduct.c
+++ b/backends/innduct.c
@@ -27,8 +27,7 @@
  *                                unlinked by duct
  *   site.name_duct.defer      431'd articles, still being written,
  *                                created, written, used by duct
- *   site.name_backlog.lock    lock taken out by innxmit wrapper
- *                                holder and its child are "xmit"
+ *
  *   site.name_backlog_<date>.<inum>
  *                             431'd articles, ready for innxmit or duct
  *                                created (link/mv) by duct
@@ -37,6 +36,12 @@
  *                             anything the sysadmin likes (eg, feed files
  *                             from old feeds to be merged into this one)
  *                                created (link/mv) by admin
+ *                                may be symlinks (in which case links
+ *                                may be written through, but only links
+ *                                will be removed.
+ *
+ *                             It is safe to remove backlog files manually,
+ *                             if it's desired to throw away the backlog.
  *
  * Backlog files are also processed by innduct.  We find the oldest
  * backlog file which is at least a certain amount old, and feed it