Yes, deleting /etc/logrotate.d/ntop will "solve" a problem like this. A more clean solution is probably to have that file indirectly deleted by purging the remains of you ntop installation. (dpkg --purge ntop)
That said, it's not necessarily the right packaging solution to have /etc/logrotate.d/ntop deleted on a non-purging package removal. From what I've seen these kinds of files are usually left alone until they are actually purged. >From what I can see this problem is caused when ntop isn't actually ran enough to generate any log files inside /var/log/ntop. Hence /var/log/ntop (being listed in debian/dirs) is automatically removed on a package deletion. If there are actually log files created once, this shouldn't be a problem, since /etc/logrotate.d/ntop contains "notifempty", preventing current logs from being rotated away once no new logs are created. ** Changed in: ntop (Ubuntu) Status: New => Incomplete -- ntop uninstall doesn't remove ntop from the log rotation https://bugs.launchpad.net/bugs/178195 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs