chiark / gitweb /
Properly document new backlog file resilience
authorIan Jackson <ian@liberator.relativity.greenend.org.uk>
Sun, 18 Apr 2010 13:48:35 +0000 (14:48 +0100)
committerIan Jackson <ian@liberator.relativity.greenend.org.uk>
Sun, 18 Apr 2010 13:48:35 +0000 (14:48 +0100)
backends/innduct.c

index 57eb9db..092c693 100644 (file)
@@ -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
  *                             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