search for: enat

I am trying to use sed to change a value in a pipe. ------------------- This is the two line script CHANGE="1234" cat my_file.txt | sed 's/CANCELID/$CHANGE/' > cancel.txt ------------------- and the my_file.txt has: <v1:notificationId>CANCELID</v1:notificationId> it gets changed to $CHANGE instead of the actual value 1234 . I tried putting a \ in front

...ash will replace $CHANGE with 1234 before starting sed with that argument. Additionally, you can avoid using "cat" to make the script more efficient. You'll start fewer processes, and complete more quickly. cat is almost never needed unless you actually need to con"cat"enate multiple files. A couple of other changes I'd suggest as better scripting style: Enclose your variable names in ${} to avoid abiguity, and use lower case variable names except when you have a variable that you mean to export, and upper case only exported variables. sed "s/CANCE...

On 08/25/2015 11:02 AM, Gordon Messmer wrote: > > Additionally, you can avoid using "cat" to make the script more > efficient. You'll start fewer processes, and complete more quickly. cat > is almost never needed unless you actually need to con"cat"enate > multiple files. I sometimes like to use cat purely for stylistic reasons : cat file.txt |\ sed -e s?"foo"?"bar"?g |\ sed -e s?"dirty"?"clean?" |\ > file2.txt It lets me line up my sed expressions. But yes, that is wasting a process fo...

Hello, I recently had to get Dovecot 1.1.4 to write to a "pop3/imap-before- smtp" db such that my MTA could permit relay after a successful authentication with Dovecot. The 'pop3' and 'imap' processes are executed only after a successful auth, so replacing them with wrappers which write to the db seemed the natural choice. Lo and behold, someone thought of

I cannot print to my Samba-printer from Win NT. Printing works fine under X-windows. What could be wrong? //Michael