[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: debug.log

Hash: SHA1

Ok, so the problem hasn't gone away. I have commented out all of the lines in the torrc file for the logging thinking that would cause no logs to be created. But it seems that the logs are being created someplace else. Where would these logs be, as they have again filled up my hard drive to 100% and I need to purge them to get my system working again.

Thanks for the assistance. The section in the torrc file relating the log files is below, and as I said I have commented out each line. Would the logs be going to the stderr or syslog as a default location. I probably should just send the logs to /dev/null just to make sure that they stop filling my hard drive.

#Log debug-info file /var/log/tor/debug.log
## Send ONLY debug messages to /usr/local/var/log/tor/debug.log
#Log debug-debug file /var/log/tor/debug.log
## Send ONLY warn messages to /usr/local/var/log/tor/debug.log
#Log debug-warn file /var/log/tor/debug.log
## To use the system log instead of Tor's logfiles, uncomment these lines:
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

Version: GnuPG v1.4.2.1 (MingW32)


On 3/3/06, Michael Holstein <michael.holstein@xxxxxxxxxxx> wrote:
> Thanks, I thought that the debug level was only for errors. Would
> commenting out all the logging levels then cause no logging to occur at
> all? Is that probably the best way to run the tor server, or should I
> have some sort of error logging in place?

Debug is too verbose, and might include information that you wouldn't
want to have around.

Doing normal logging (>warn) is fine .. only generates a few errors when
people try dumb stuff like CONNECT:port against your DirPort, and when
you have network writes that fail (although is scrubbs the address from

I run a fairly busy exit node, and my log only grows by 100k or so a day
(which newsyslog can rotate around).