You could try the following - if you have a working server with the same software installed.
***IMPORTANT*** I would advise testing this on an unimportant directory on the server prior to a full run if at all possible. All I can say is it can't really make things any worse.
On the WORKING server;
find / -type f -exec ll {} \; | awk '{print substr($0,2,3)":"substr($0,5,3)":"substr($0,8,3)":"$NF}' | sed -e s/"\-"//g > /tmp/perm_list.txt
This will generate a list of permissions (separated into owner, group and other by a colon), and files eg
rwx:rx:rx:./test/getuser
rw:r::./test/bits/dept
rwx:rwx:rwx:./test/bits/test
rwx:rx::./test/bits/checker
rw:r::./test/bits/1
rw:r::./test/bits/1.c
rw:r::./test/non_patrol
rw:r::./test/sys.lst
rw:r::./test/local.lst
rw:rw:rw:./test/local_ser
This can then be copied to the AFFECTED server.
You can then try the following to set the permissions. *** ENSURE THAT YOU ARE ON THE AFFECTED SERVER ***
for LINE in `cat perm_list.txt`
do
USER=`echo $LINE | awk -F: '{print $1}'`
GROUP=`echo $LINE | awk -F: '{print $2}'`
OTHER=`echo $LINE | awk -F: '{print $3}'`
FILE=`echo $LINE | awk -F: '{print $4}'`
echo "setting file permissions to $USER$GROUP$OTHER for $FILE"
chmod u=$USER,g=$GROUP,o=$OTHER $FILE
done
What this is doing, is taking each line from the list on the working server, and setting the same permissions to the files on the affected server (if they exist).
Hopefully, this will address most of the problems, but if it doesn't work, you will have to look to a full restore.
It may be worth waiting to see if anyone else has comments on this approach before trying it.
Good luck.
