While bridging our account management scripts between the old auth files
and then new auth.db, we were using edauth -s to install extended
attributes and passwords for new users. After placing edauth -r in a
script to remove users, we can no longer use edauth to read or edit the
database. Users continue to login, and the database timestamp updates
whenever passwords are changed, it seems only edauth is broken.
But, without edauth, we can't change or view the attributes. After
running with the new system for a couple of weeks, we are reluctant to
reload from the old database files because of changed passwords, etc.
The system has about 10000 users.
Anyone know how to repair edauth/auth.db in place?
--
Larye D. Parkins, Systems Administrator
Computing & Information Services
University of Montana, Missoula, MT 59801
(406) 243-2486 larye_at_selway.umt.edu
Received on Tue Jan 11 2000 - 00:37:57 NZDT