No, replacing 192.1.2.11 with 192.1.2.13 so I guess
find . -type f -name '*'|xargs grep -lF 192.1.2.11 {} |xargs -t -I {} vi -c s/192.1.2.11/192.1.2.13/g -c wq {} 2>IPchange.err
would work?
Thanks
Chris
Why isn't it possible to run a stored procedure via a job in SQL Server Agent which references a table whose name includes ampersand (&) but it works if you perform exactly the same operation in query analyzer?
Hmmmmm.......
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.