From: Sun Fire (starcat524@yahoo.com)
Date: Mon Apr 17 2006 - 02:25:48 EDT
Dear Sun Managers,
I just created a generic account (bbusr) and under the
account security for passwd, I selected 'No password
-- setuid only' so that nobody can logon to the server
using this generic account. All my unix users who wish
to logon to this generic account goes via sudo access
to switch user to this generic account. The main
purpose of this generic account is meant for user to
create cron jobs under this account. However, I found
under the cron log that the passwd has expired for
this generic account and it's cron jobs failed.
My question is why does the unix account created using
'setuid only' still encounter passwd expiry issue in
the cron. Why do I need to change the passwd since
it's not supposed to have any passwd in the first
place?
The following shows the unix account for bbusr is
created wihout any passwd.
# grep bbusr /etc/shadow
bbusr:NP:13193:0:60:5:::
The following from the cron log shows the cron job
failed to run due to passwd expiry.
# grep "user (bbusr) password has expired" olog
! user (bbusr) password has expired Sun Apr 16
03:01:00 2006
! user (bbusr) password has expired Sun Apr 16
03:01:00 2006
! user (bbusr) password has expired Mon Apr 17
03:01:00 2006
Or should I manually change the entry in /etc/shadow
from bbusr:NP:13193:0:60:5:::
to bbusr:NP:6445::::::
Thanks in advance for your help.
Regards,
Andrew
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:39:36 EDT