Thanks and he had the correct owner. Not sure what happen, but the issue was
corrected. Like I said, an @ sign ended up on the owner's name if I recall
correctly. Either way, something got hosed, but we got it cleared up.
Permissions can be a funny thing and sure can cause some problems. :)
tnx
My guess is he needs to change the owner of the file. If you do an ls -l
on files in both locations it should list an owner name which should be
the shortname for the account, along with the permissions. Might want to
do a man on chown and chgrp which are the commands to change a file's
owner a
