Package: cron Version: 3.0pl1-116 I have just been bitten by #625491.
It is now of course too late to revert this ill-advised change. (The only worse thing than cron jobs unexpected not running would be zombie cron jobs from years gone by suddenly rising from the dead.) However, there should be a way to disable this check. That way when one edits or creates files with a 002 umask (as is usual) the cron jobs will actually run. -- Ian Jackson personal email: <[email protected]> These opinions are my own. http://www.chiark.greenend.org.uk/~ijackson/ PGP2 key 1024R/0x23f5addb, fingerprint 5906F687 BD03ACAD 0D8E602E FCF37657 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
