>You should be able to remove or edit /etc/cron.d/certbot, and by policy packaging is required to respect your change. Does this not work?
Yes, this appears to work (at least, after removing the file, `apt-get install --reinstall python3-certbot` on disco doesn't recreate it), but as I understand it, this is a non-standard mechanism for disabling a cron job. In the past the standard mechanism has been to include a variable in /etc/default/[whatever] to indicate whether the cron job should run. I don't want to delete files from the source package. What happens if I decide to switch back to the packager's version of the cron job later, but the file is gone because I deleted it to prevent it from running? >(and similarly you should be able to disable the systemd certbot.timer using systemd's usual mechanisms, and this change should also be preserved by packaging) I suppose this is actually the correct answer in the age of systemd. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706409 Title: should be possible to disable certbot cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1706409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
