The running 'sdemon' process "remembers" the password used to start it, so if you
change the SDE user password while it's running, you can't use the new password
to stop it.
There's little risk of corrupting the metadata tables in the SDE user if you've done
something to corrupt the application server install (if it can't connect, it can't hose
the tables).
'sdemon -o info' communicates directly with the giomgr daemon process (without
a password), so it would not be affected by a password change.
- V