On Wed, Apr 06, 2005 at 05:47:44PM -0500, Steve Greenland wrote: > On 06-Apr-05, 14:45 (CDT), Gerrit Pape <[EMAIL PROTECTED]> wrote: > > There'll be two binary packages: bcron, containing the bcron programs > > and documentation, and bcron-run, setting up the bcron services, and > > providing, replacing, and conflicting with the default cron package. > > It looks like bcron messes with the permissions and structures of > /var/spool/cron/crontabs. Are you going to handling conversion between
Yes, with bcron this directory and the files in it are all owned by a system user 'cron' and have restricted permissions. The bcron-run.postinst will take care of this when switching from cron to bcron. > the two (cron and bcron)? In particular, are you going to convert > *back* on removal of bcron-run? Or do you expect cron to clean it up on > re-install? (I can handle that, but I'd like to know the plan.) My plan was to file a wishlist bug against your cron package after preparing and testing a patch against its postinst. It would be nice if the cron package can handle the conversion back, I think; similar to how it adjusts permissions of /var/spool/cron/crontab/* on upgrade from << 3.0pl1-81. Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]