Your message dated Wed, 5 Sep 2012 18:06:56 +0200 with message-id <[email protected]> and subject line Re: Bug#686512: atop: init script creates file '/var/log/atop/daily.log' has caused the Debian Bug report #686512, regarding atop: init script creates file '/var/log/atop/daily.log' to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 686512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686512 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: atop Version: 1.26-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Nightly cron job '/etc/cron.d/atop' executes atop _cron * What exactly did you do (or not do) that was effective (or ineffective)? N/A * What was the outcome of this action? The nightly cron script invokes the init script which restarts the atop daemon and starts writing to a new log file named /var/log/atop/atop_YYYYMMDD. In the process of doing so it creates an empty file '/var/log/atop/daily.log' which is never written to. * What outcome did you expect instead? No '/var/log/atop/daily.log' file. It is redundant and confusing. AFAICS atop doesn't take a file name without a preceding read (-r) or write (-w) argument, but the wrapper script has redirected the output there for some reason. Perhaps the daily log is there to hold error messages from the restart, but if that is the case it should perhaps be named 'error.log' to eliminate confusion. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.23-interatom (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages atop depends on: ii libc6 2.13-35 ii libncurses5 5.9-10 ii libtinfo5 5.9-10 ii lsb-base 4.1+Debian7 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages atop recommends: ii cron 3.0pl1-124 atop suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Sun, Sep 02, 2012 at 10:38:10AM -0400, Dominique Brazziel wrote: > The nightly cron script invokes the init script > which restarts the atop daemon and > starts writing to a new log file named > /var/log/atop/atop_YYYYMMDD. In the process > of doing so it creates an empty file > '/var/log/atop/daily.log' which is never > written to. That means that your atop is not encountering anything special that it finds worth logging. This can happen. On many systems, it is even the normality. Closing the bug report. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062
--- End Message ---
