implement cluster.log
Not used yet. (Or tested.) I did consider making the log start with the uuid of the node, followed by the cluster uuid (or uuids). That would perhaps mean a smaller write to the git-annex branch when adding a node, but overall the log file would be larger, and it will be read and cached near to startup on most git-annex runs.
This commit is contained in:
parent
01f5015f30
commit
aa56d433d5
6 changed files with 135 additions and 7 deletions
|
@ -13,8 +13,6 @@ module Logs.Proxy (
|
|||
recordProxies,
|
||||
) where
|
||||
|
||||
import qualified Data.Map as M
|
||||
|
||||
import qualified Annex
|
||||
import Annex.Common
|
||||
import qualified Annex.Branch
|
||||
|
@ -26,6 +24,7 @@ import Logs.MapLog
|
|||
import Annex.UUID
|
||||
|
||||
import qualified Data.Set as S
|
||||
import qualified Data.Map as M
|
||||
import Data.ByteString.Builder
|
||||
import qualified Data.Attoparsec.ByteString as A
|
||||
import qualified Data.Attoparsec.ByteString.Char8 as A8
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue