In my earlier message, I noted that running msec after setting
password_aging(-1) in the level.local file was giving a message, "msec:
unable to parse chage output," when running msec. The first time I ran it
after setting that value, I didn't get the error message - only on
subsequent runs. I've been watching the syslog, and when running msec, it
does a "/bin/chage -l {user}" for each user. Now, when I first set
password_aging(-1), it was just fine and it ran chage with the option to
inactivate password aging. After that, however, it doesn't seem to like
the "-1" coming out of the list when chage -l {user} is run. I can only
get rid of the message (and can only change password aging via msec) after
this by manually running chage and setting maxage to a positive number.
It looks like msec doesn't know what to do with a -1 when it tries to list
the current password aging when it is run.
--Dave
--
David Guntner GEnie: Just say NO!
http://www.akaMail.com/pgpkey/davidg or key server
for PGP Public key
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
