At 06:24 AM 5/6/02, Dave Naylor wrote: >Hi > >When cron.hourly is run on my machine, I get an email telling me:- > >"msec: unable to parse chage output" > >This seems to be generated from /usr/share/msec/libmsec.py after trying to: > >cmd = '/usr/bin/chage -M %d -I %d %s' % (max, inactive, entry[0]) >ret = commands.getstatusoutput(cmd) > >I wondered if, because I hadn't set any expiry times for passwords on my >system, this is where the error message was coming from. Setting expiry >times though didn't help. > >Anyone point me in the right direction. The hourly mails are getting a >little >irritating. Redirecting them to dev/null seems a chickens way out :)
Dave, This issue has been addressed here and a patch was posted to this list. There's a mismatch between new user entries created by webmin, how chage processes the entries, and how msec processes the output of chage. There's a patch for msec so that it will accept chage's output. Look for a message from 3/30 titled "msec vs. webmin - and a patch". HEY MANDRAKE PEOPLE! HOW ABOUT RELEASING THE FIX FOR MSEC !!!!! This is at least the second query about this same issue since I generated the patch over a month ago. David
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
