[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#128795: suck: Incomplete uninstall



* Paul Martin 

| reassign 128795 suck
| thanks

I disagree, obviously.  Taking this to debian-devel, since I doubt we
can agree.  Therefore quoting a fair bit as well.

| On Sat, Jan 12, 2002 at 08:32:02PM -0800, Ross Boylan wrote:
| > On Sat, Jan 12, 2002 at 08:51:20PM +0100, Tollef Fog Heen wrote:
| 
| > > | I uninstalled suck (apt-get remove) but it seems some cron jobs are
| > > | still hanging around.  Here's the log:
| > > 
| > > Uhm, no.  It's actually just a logrotate hanging around, which is
| > > should, according to policy.
| > 
| > Right; it was the logrotate entry.  logrotate was the cron job, which
| > obviously needs to continue.
| 
| > > I am reassigning this bug against logrotate since it shouldn't report
| > > errors for files which have ?missingok? enabled.
| 
| Unfortunately, this only applies to files for which there is no
| wildcard. The error is reported *before* the missingok has been parsed.

The documentation does not say _anything_ about that.  It says that

       missingok
              If the log file is missing, go on to  the  next  one  without
              issuing an error message. See also nomissingok.

/var/log/suck/*log

is missing and the missingok directive is present.  That means that it
should _not_ issue an error message.

And an example from the man page shows:

       /var/log/news/* {
           monthly
           rotate 2
           missingok
           postrotate
               kill -HUP `cat /var/run/inn.pid`
           endscript
           nocompress
       }

Why would there be a missingok there if it didn't have any effect?

(And before you go about changing the documenation, when a program
doesn't behave according to the docs, it's the program, not the docs
which need changing)

| Sorry, Tollef, but this isn't a logrotate bug. It looks like Ross has
| removed /var/log/suck by hand. Neither 'dpkg --remove' nor 'apt-get
| remove' should have removed that directory.

He said he didn't though.

| Ross: Run "dpkg --purge suck", and that should get rid of the
| troublesome logrotate entry.

True, but looks like this uncovered a bug (or at least I call it a
bug) in logrotate as well.

-- 
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about who its friends are.



Reply to: