On Wed, Dec 6, 2017 at 6:12 PM, Paolo Gigante wrote: > As per the ITP (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880600) > there is a lot of additional functionality that auter provides which goes > way beyond what is offered by cron-apt and unattended-upgrades:
A comment on the ITP features: > This allows servers to be configured to stop any critical > applications cleanly using custom scripts before any actions are taken. Critical applications should be cleanly integrated with the system so that normal shutdown/reboot does the right thing. > - Auter has the functionality to separate download schedules from install > schedules which is great for organisations wanting to version control > updates across multiple servers and environments while staggering the update > process for the servers. This is also supported by unattended-upgrades under systemd. > - It also allows for customised scripts to be executed pre and post > downloading updates, applying updates and rebooting the server This is also supported by apt, except reboot hooks but those should probably be integrated into the init system instead. > - It has the option to automate reboots after the patching process has been > applied This is also supported by unattended-upgrades, including a set reboot time. > - There is an option of setting up multiple patching profiles eg: weekly > application patches and monthly system/kernel patching (This is entirely > customiseable) In theory this could be possible with unattended-upgrades but I think it would be hard to setup. > - In cases where admins have multiple servers with different rehdat or > debian based distributions, the same application and configuration files can > be deployed to servers regardless of the distribution. That seems like a plus for those stuck in that situation indeed. -- bye, pabs https://wiki.debian.org/PaulWise
