Sorry for the lack of informations, trafficserver version 2.0.0a configuration for logs: # possible values for logging_enabled: # 0: no logging at all # 1: log errors only # 2: log transactions only # 3: full logging (errors + transactions) CONFIG proxy.config.log2.logging_enabled INT 2 CONFIG proxy.config.log2.max_secs_per_buffer INT 5 CONFIG proxy.config.log2.max_space_mb_for_logs INT 25000000 CONFIG proxy.config.log2.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log2.max_space_mb_headroom INT 3000 CONFIG proxy.config.log2.hostname STRING localhost CONFIG proxy.config.log2.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log2.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log2.custom_logs_enabled INT 0 # 0: old log format, 1: new xml log format (default) CONFIG proxy.config.log2.xml_logs_config INT 1 CONFIG proxy.config.log2.squid_log_enabled INT 1 CONFIG proxy.config.log2.squid_log_is_ascii INT 1 CONFIG proxy.config.log2.squid_log_name STRING squid CONFIG proxy.config.log2.squid_log_header STRING NULL CONFIG proxy.config.log2.common_log_enabled INT 0 CONFIG proxy.config.log2.common_log_is_ascii INT 1 CONFIG proxy.config.log2.common_log_name STRING common CONFIG proxy.config.log2.common_log_header STRING NULL
Le 30 mars 2011 à 15:55, Leif Hedstrom a écrit : > On 03/30/2011 06:51 AM, Belkacem wrote: >> and also stoped logging in squid.log (ascii logging) > > > I think we'd need some more details here. There are many ways logs can get > deleted, for example, if disk got filled up. There are many configurations > that would control all the rotation and retention policies. Also, it'd help > to know what version you are using, platform, etc. etc. > > -- Leif >
