Closed (fixed)
Project:
Provision
Version:
7.x-3.x-dev
Component:
Install process
Priority:
Major
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Aug 2011 at 18:07 UTC
Updated:
18 Nov 2015 at 20:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
anarcat commentedThat is a great idea! We could have special markers in the crontab text to mark the automatically managed entries, a bit like what Puppet does... and only edit the entries within those markers.
Comment #2
steven jones commentedComment #3
ergonlogicNew features need to be implemented in Aegir 3.x, then we can consider back-porting to Aegir 2.x.
Comment #4
omega8cc commentedWhy not to simply use
/etc/crontabfor custom entries you don't want to get overwritten?Comment #5
helmo commentedThe Debian package could easily handle a static cron file.
The code where we generate the contents for the crontab entry, however is now in the hosting package. In the 'hosting-setup' drush command.
And I don't want to do that in two places.
Letting Aegir edit a file in /etc/cron.d is not so nice in terms of security ... So the best option I see is to create some php code that can safely remove our old cron lines.
Comment #6
helmo commentedComment #7
helmo commentedAnd with some more documentation.
This should remove our old lines, and add the new ones at the bottom.
Comment #8
helmo commentedComment #9
gboudrias commentedSeems to work pretty well.
Comment #10
helmo commented