No cron restart after pam upgrade?

[Simon Males]

Hello,

I just had three 10.10 servers perform an unattended-upgrade to
libpam* and all three servers started producing the following errors
in syslog:

CRON[31500]: Module is unknown

Restarting cron brought things back to life.

There are a number of different threads (not Ubuntu specific)
detailing a similar situation: Cron error on libpam upgrade.

Is it a fair suggestion that cron should restart on a libpam upgrade?

-- 
Simon Males