1 of 1 people found this helpful
nsh does not use the gnu sed so the arguments are different. i'm assuming you are using the gnu sed there. check the man page for sed in nsh and what you need to supply to the -i argument.
Yes Bill, I read the man page seperately on NSH and BASH.
sed -i on NSH:
Edit files in-place similarly to -I, but treat each file independently from other files.
In particular, line numbers in each file start at 1, the "$" address matches the last line
of the current file, and address ranges are limited to the current file. (See Sed
Addresses.) The net result is as though each file were edited by a separate sed instance.
sed -i on BASH:
edit files in place (makes backup if extension supplied)
It seems, sed on NSH requires an extension for a backup. It worked fine for me after I added extension to -i.
ServerXYZ# sed -i bkp "s/226/231/g" disk_cleanup.sh
ServerXYZ# ls -l disk_cleanup*
-rw-r--r-- 1 bladmin bladmin 892 Feb 17 21:44 disk_cleanup.sh
-rwxr--r-- 1 bladmin bladmin 892 Feb 17 00:29 disk_cleanup.shbkp
Thank you, Bill.!