> but passwd said "conversation error". anoy way it doesn't work. So
> anyone know how to handle this kind of problem? or in an alternative
> way to work the task out.
asdf^Jasdf | passwd either). I'd expect it to be a bit smarter and give a
reasonable error message when stdin isn't a tty.
My RH6.1 system has a chpasswd util which you might try using. If you're
pickier about security, you could even call crypt yourself (seeding it with
your own random salt) and use chpasswd -e.