Anyone doing unattended upgrades in production opens themselves up to this sort of risk. Sure it was a screwup by Ubuntu, but would have been easily resolved if you'd done upgrades in a scheduled maintenance window. All aboard thye failboat.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790538 Title: pam update causes cron to stop working with "Module is unknown" error -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
