Bug 56664

Summary:	dspam-3.0.0: cron job left behind after unemerge
Product:	Gentoo Linux	Reporter:	Phil Richards <news>
Component:	Current packages	Assignee:	Net-Mail Packages <net-mail+disabled>
Status:	RESOLVED WONTFIX
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Phil Richards 2004-07-11 03:01:48 UTC

I installed dspam-3.0.0 to have a play with; having finished my games, I unmerged it.

This morning I received an alert from cron telling me that /etc/cron.daily/dspam.cron had errors - hardly surprising since dspam was supposed to have no longer existed/be active.

Is this a consequence of CONFIG_PROTECT?  If so, it appears an undesirable one.

phil

Comment 1 Grant Goodyear (RETIRED) gentoo-dev

2004-07-12 21:29:50 UTC

You're quite right, it is an effect of CONFIG_PROTECT.  If you would prefer that
files in the cron directories not be protected, you may add them to CONFIG_PROTECT_MASK.  

I'm going to mark this bug WONTFIX because I think the simplicity of CONFIG_PROTECTing all files in /etc outweighs the cosmetic bug of cron files not being removed by emerge unmerge (which is easy for the user to fix and the user is even reminded by cron sending an e-mail when it fails).

If you disagree, feel free to start a discussion on gentoo-dev@gentoo.org.