Package: tor Version: 0.2.5.8-rc-1 Severity: normal Hello,
I run tor only occasionally and so it happens that logrotate kicks in while tor is not running. As long as there is no tor-log to rotate everything is fine but if a tor-log needs to be rotated, I get the following message from cron: | /etc/cron.daily/logrotate: | error: error running shared postrotate script for '/var/log/tor/*log ' | run-parts: /etc/cron.daily/logrotate exited with return code 1 Thats because logrotate tries to reload tor and its init script will bail out with an error message and code if tor isn't running. So it would seem the best to check in /etc/logrotate.d/tor's postrotate section if tor is actually running before trying to reload it. Regards, Dirk -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tor depends on: ii adduser 3.113+nmu3 ii libc6 2.19-11 ii libevent-2.0-5 2.0.21-stable-1.1 ii libseccomp2 2.1.1-1 ii libssl1.0.0 1.0.1i-2 ii lsb-base 4.1+Debian13 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages tor recommends: ii logrotate 3.8.7-1 pn tor-geoipdb <none> pn torsocks <none> Versions of packages tor suggests: pn apparmor-utils <none> pn mixmaster <none> pn obfsproxy <none> pn polipo | privoxy <none> pn socat <none> pn tor-arm <none> pn xul-ext-torbutton <none> -- Configuration Files: /etc/tor/torrc changed: SocksPort 0 AutomapHostsOnResolve 1 TransPort 9040 DNSPort 53 ExitPolicy reject *:* # no exits allowed -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
