Ubuntu
cron package

  1. Maverick (10.10)
  2. Bug #27520
  3. Comment #0

Comment 0 for bug 27520

Revision history for this message
Tessa (unit3) wrote : cron no longer respects nsswitch.conf

We had a server which was happily running Hoary. It authenticated to our AD2003
domain using winbind, and winbind was in the nsswitch.conf. However, after
upgrading to Breezy, cron no longer works properly, in that it doesn't respect
accounts from winbind as being valid accounts. My logs are filling up with
messages like:

Dec 22 09:52:01 thorin /usr/sbin/cron[28207]: (user1) ORPHAN (no passwd entry)
Dec 22 09:52:01 thorin /usr/sbin/cron[28207]: (user2) ORPHAN (no passwd entry)
Dec 22 09:55:01 thorin /usr/sbin/cron[28207]: (user3) ORPHAN (no passwd entry)
Dec 22 09:55:01 thorin /usr/sbin/cron[28207]: (user4) ORPHAN (no passwd entry)

If you do "id user1", their information shows up perfectly fine, so it seems
like cron has been changed to not respect this source of information.