HowTo....
Tinkering is what I did... I always like posting findings so here's what I did... files I edited... etc in case other have this need.
1) backup these files before doing what I've done, just in case
2) continue...
[Renaming User] (in my case a reseller)
usermod -d /home/newname oldname
#sets new home directory. File affected: /etc/passwd
usermod -g newname oldname
#sets intial group.
groupmod -n newname oldname
#changes the group name. File(s) affected: /etc/group & /etc/gshadow
cat /etc/passwd |grep newname
#this verifies the home directory was set properly (displays)
[Move old home directory to new directory]
mv /home/oldname /home/newname
[Change Apache to point to new home location]
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
replace /home/oldname/ /home/newname/ -- /etc/httpd/conf/httpd.conf
#This replaces the individual path for Apache to load the new location's individual httpd.conf settings
replace oldname newname -- /etc/httpd/conf/ips.conf
#makes sure to replace the normally 'auto-generated' file here, otherwise apache will give errors
/etc/rc.d/init.d/httpd restart
# restart appache to take affect
# Also note, if you don't use that script, you'll probably get SSLEngine errors when restarting apache.
[Change FTPD info]
replace oldename: newname: -- /etc/proftpd.passwd
#Notice the colon's at the end of the names, keep those but change the names as needed
#NOTE:
#if by chance the UID in /etc/proftpd/passwd is 9999:9999: you will need to put in the original UID, found simply by typing:
#ls -n /home/
#... this should return a number (probably a 500'ish number) replace both sets of 9999 with that number.
service proftpd restart
#restart proftpd
---- someone with a bit more skill than I could easily write a script to take care of all these changes simply prompting the user for two vars.. 1) old name to change, 2) new name to be...
*wink?*
Far as I know these should do the trick. If anyone else can think of any other changes that need to be done, lemmie know.