X-Git-Url: https://iankelling.org/git/?a=blobdiff_plain;f=epanic-clean;fp=epanic-clean;h=8c26855041437f27fb4de093a5432ec64d4739d7;hb=12cab163424e3a7b0815646d1d4407f9b5839bcb;hp=a7220c2cf03267c2c2aacdd6822c172537d2d297;hpb=5e45ae077e790c0e798f09ffad8ecd3cb6c3bb28;p=distro-setup

diff --git a/epanic-clean b/epanic-clean
index a7220c2..8c26855 100755
--- a/epanic-clean
+++ b/epanic-clean
@@ -38,8 +38,8 @@ main() {
   grep "$regex" $pl >> $pl-archive ||:
   sed -i "/$regex/d" $pl
 
-  ## begin broken pipe ##
-  regex="Failed writing transport results to pipe: Broken pipe$"
+  ## begin broken pipe & write lock ##
+  regex="Failed to get write lock\|Failed writing transport results to pipe: Broken pipe$"
   now_s=$(date +%s)
   newlines=false
   count=0
@@ -51,11 +51,11 @@ main() {
     fi
   done < <(grep "$regex" $pl ||:)
   if (( count )); then
-    # i see these in groups of 3 for the same message around once a day
+    # I see broken pipe in groups of 3 for the same message around once a day
     # randomly.  I'm guessing they are related to running 2 instances of
     # exim which share the same spool.  So, if we have some, but not in
     # the last 5 minutes, and less than 20, it should be fine to clear
-    # them.
+    # them. write lock happens less but can fit under the same rule.
     if (( count > 20 )); then
       cat $pl
       elif ! $newlines; then