Many 代管 providers claim to keep no 日誌, but the term is often used loosely. Some providers disable application 日誌 while retaining 系統 日誌, netflow 數據, or SNMP statistics that reveal connection patterns. Others maintain 帳單 records that can be correlated with 流量 timestamps. True 無日誌s 代管 must address every layer of the stack where 數據 could be recorded.
At AnubizHost, 無日誌s means exactly that: zero 流量 數據 is recorded at any level. Our 伺服器s are configured with disabled syslog for 網路 interfaces, no netflow or sFlow export, no SNMP 流量 counters, and no application-level 日誌記錄 of connections. We do not even maintain 頻寬 usage statistics for individual 伺服器s beyond what is necessary for aggregate capacity planning.
Our approach goes beyond policy - it is architectural. 伺服器s boot from read-only images with 日誌記錄 directories mounted as tmpfs file系統s that exist only in RAM. In the event of a power interruption or seizure, all temporary 數據 is immediately and irrecoverably lost. There is simply no persistent storage location where 日誌 could accumulate.