The /home directory seems to be ok....but most other directories are 000. I've gone through and tried to match as many of them as I can to another server, but not with much luck....asmithjr said:
Some of the hard ones are like the /dev folder.....well all of the files in that folder.
I think the main problem isn't the folders themselves, but all of the files inside those folders iwth the different permissions.....
I think we are screwed....
I believe you can use the rdist command to copy files and perms over, that is if you can do r type commands from machine to machine.
either rdist or rsync might do the trick.
Other than that you need a listing of the perms before.
I'll keep thinking. but the rsync looks promising
take a look at the rcync man page.
either rdist or rsync might do the trick.
Other than that you need a listing of the perms before.
I'll keep thinking. but the rsync looks promising
take a look at the rcync man page.
Code:
You use rsync in the same way you use rcp. You must specify a source
and a destination, one of which may be remote.
Perhaps the best way to explain the syntax is some examples:
rsync *.c foo:src/
this would transfer all files matching the pattern *.c from the current
directory to the directory src on the machine foo. If any of the files
already exist on the remote system then the rsync remote-update proto-
col is used to update the file by sending only the differences. See the
tech report for details.
rsync -avz foo:src/bar /data/tmp
this would recursively transfer all files from the directory src/bar on
the machine foo into the /data/tmp/bar directory on the local machine.
The files are transferred in "archive" mode, which ensures that sym-
bolic links, devices, attributes, permissions, ownerships etc are pre-
served in the transfer. Additionally, compression will be used to
reduce the size of data portions of the transfer.
rsync -avz foo:src/bar/ /data/tmp
a trailing slash on the source changes this behavior to transfer all
files from the directory src/bar on the machine foo into the
/data/tmp/. A trailing / on a source name means "copy the contents of
this directory". Without a trailing slash it means "copy the direc-
tory". This difference becomes particularly important when using the
--delete option.
You can also use rsync in local-only mode, where both the source and
destination don´t have a ´:´ in the name. In this case it behaves like
an improved copy command.
rsync somehost.mydomain.com::
this would list all the anonymous rsync modules available on the host
somehost.mydomain.com. (See the following section for more details.)I think i got it:asmithjr said:
From the good server:
# rsync -avz -e ssh /dev/ [email protected]:/dev/
rpm --setperms -a ornoimad1 said:
rpm --setugids -a
sets all the files/folders ownership, permission and modes to their default. Now, for your home directory and any other manually installed stuff, you have to do separately.
Jemshad O K
Bobcares
I really don't think you want to rsync /dev from another box.. That might cause you a problem.
is a good idea.
You could always try to run /dev/MAKEDEV $options (to rebuild /dev)
# man MAKEDEV (for more info)
As posted by The man who cares
is a good idea.You could always try to run /dev/MAKEDEV $options (to rebuild /dev)
# man MAKEDEV (for more info)
Last edited:
Thanks guys...yea I had already done some of the rsyncs and that did cause some problems....like I overwrote my mysql database file that holds all of the mysql users and passwords....that is another mess I'm having to clean up.Jemshi said:
I found out the only directory I had left that was causing me problems was the actual ./ directory....took me a long time to find that one....
Thanks again for the help!
Can someone tell me why .* caused it to go up to a higher directory? Does that .* signify root directory? If I try ls . I get a listing for current directory, but if I try ls .* I get a listing for root directory.noimad1 said:
single dot (.) is your current directory and
double dot (..) is the parent directory
so giving .* includes .. also. Better method to include all the files and folders (starting with dot too) is
chmod -R user.group directory
from its parent directory. And if you want to spare the directory, revert it back with
chmod olduser.oldgroup directory
Or, standing inside the directory,
find . -exec chmod user.grop {} \; will also give the same result
HTH
double dot (..) is the parent directory
so giving .* includes .. also. Better method to include all the files and folders (starting with dot too) is
chmod -R user.group directory
from its parent directory. And if you want to spare the directory, revert it back with
chmod olduser.oldgroup directory
Or, standing inside the directory,
find . -exec chmod user.grop {} \; will also give the same result
HTH
This is actually a common mistake ... I restored a server just at christmas, Christmas day for a client that did this
< EDIT referred back to ticket - this is what happened in my case with one client >
# ls -la /tmp
# rm -rf *
Only he wasn't in /tmp - he was in /
</ EDIT>
Believing that it would delete all files in /tmp that were prefixed with .
You should really use the full system path to files when using wildcard deletes and chmod's, it's good practice.
for a client that did this< EDIT referred back to ticket - this is what happened in my case with one client >
# ls -la /tmp
# rm -rf *
Only he wasn't in /tmp - he was in /
</ EDIT>
Believing that it would delete all files in /tmp that were prefixed with .
You should really use the full system path to files when using wildcard deletes and chmod's, it's good practice.
Last edited:
I don't know if it was the .* by itself. I'm pretty sure it was the -R (recursive) that killed it. Becuase the .* by itself should only change the directory you are currently in. But the recursive does the directory you are in and then goes above it and does all directories above it and so on....Finley Ave said:
dianaward said:
I believe the .* will actually do the . and the .. - so it will do the current directory and parent directory and anything above it.
Needless to say I have learned my lesson on this one and will be much more careful when it comes to these types of edits....I just got in a hurry and wasn't paying attention.
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| S | big problem | File Management | 2 | |
| B | cPanel space and BW calculation BIG Problems! | File Management | 1 | |
| D | Big Problem with 1 account | File Management | 13 | |
| B | Big Problems - CHOWN Issue | File Management | 1 | |
| B | Big reseller´s permission problem | File Management | 11 |