nobaloney
NoBaloney Internet Svcs - In Memoriam †
Amit,
NOTE that anything you do while logged in through ssh can completely destroy your entire system. BE CAREFUL.
What you're really trying to do is quite simple, but the problem is you have no frame of reference from which to try any of the suggestions given.
So here's my attempt to give you a frame of reference...
You use ssh the same way you use the DOS shell under Windows, the difference being that you use ssh across the net.
So the first thing to do is to log into your server, using ssh, and a login that gives you enough rights to change the files you need to change.
Unless all the files are owned by the same user that will have to be root.
Once you're logged in either as root, or as the user that owns all the files you now have to identify the files.
Do you know where all these files are located? Do you know where they are?
Can you create a path, using wildcards, that will help you identify all the files?
For example, while logged in as root, would /home/*/domains/*/public_html/*.html be a good wildcard that will identify all the files?
Are all the changes to be made from one specific path to another specific path?
If so you can use some of the ideas given.
If not, you'll have to start explaining the differences between what I've written and your actual environment.
Jeff
NOTE that anything you do while logged in through ssh can completely destroy your entire system. BE CAREFUL.
What you're really trying to do is quite simple, but the problem is you have no frame of reference from which to try any of the suggestions given.
So here's my attempt to give you a frame of reference...
You use ssh the same way you use the DOS shell under Windows, the difference being that you use ssh across the net.
So the first thing to do is to log into your server, using ssh, and a login that gives you enough rights to change the files you need to change.
Unless all the files are owned by the same user that will have to be root.
Once you're logged in either as root, or as the user that owns all the files you now have to identify the files.
Do you know where all these files are located? Do you know where they are?
Can you create a path, using wildcards, that will help you identify all the files?
For example, while logged in as root, would /home/*/domains/*/public_html/*.html be a good wildcard that will identify all the files?
Are all the changes to be made from one specific path to another specific path?
If so you can use some of the ideas given.
If not, you'll have to start explaining the differences between what I've written and your actual environment.
Jeff