I was in a folder that i created called /downloadsasmithjr said:where were you in / ?
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:I see the .* did it.
what does ls -l / give you
I can give you what I have for the directories but by no means for the entire drive,
If you look into /home for instance and see everything 000 bad news.
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.)
Can you help me out on the syntax of that a bit?asmithjr said: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.
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:I believe it would be,
From your good server:
# rsync -avz /dev/ badserver:/dev/
not sure if you need the goodserver but pretty sure you need the / infront of dev
rpm --setperms -a ornoimad1 said:I was working in a directory and I accidently put chmod -R 000 .*
A lot of my root files and subfolders were chmod 0000!
Anyone know how I could get the regular permissions back, or am I going to have to reload the entire server?
As posted by The man who caresrpm --setperms -a or
rpm --setugids -a
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:rpm --setperms -a or
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 decided to go ahead and run those commands anyways, but I received these errors:Jemshi said:rpm --setperms -a or
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
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:I was working in a directory and I accidently put chmod -R 000 .*
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: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.
dianaward said:directory-wise???
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 |