Hi,
I am familiar with using a backslash to escape a $ in a send command, but this device I am using expect to talk to has a regex expression that I need to input and it is a bear. Is there a list of all the characters that require escaping in an expect send statement ? Here is what I need to 'send'.. Pretty gross huh ?
Thanks
---------- Post updated at 10:44 AM ---------- Previous update was at 10:43 AM ----------
Welcome to the forum ob2s. If you run autoexpect and at the command prompt type a pound sign so the OS doesn't do anything with your junky string and then paste it. Type exit and you will see the send command it created out of your junky string. Take that line and paste it into vi and then paste the original string under and do stare and compare to see what it escaped since autoexpect has escaping coded into it.
You will want to run the script.exp it produced and write the output to a file to make sure it is exact the same.
Good luck.
how do i unescape special characters in Unix.
Suppose i've a file named -xyz.txt, how do I remove the file.
Ofcourse Icant give rm -xyz.txt thats not gonna work.
We can go in regular expression like this ls | grep -e '-'xyz.txt | rm; but I'd like to know any simpler way than this.
Thanks... (3 Replies)
Hi there
I need to grep for a detail from a file. The pattern to search for involves escape sequences in it. This causes for the problem.
grep "P\_SOME\_STRING\_SEARCH" filename
Note, I have line like below in the file and expect it to grep.
select *
from my_system_param
... (3 Replies)
When I open a file in vi, I see the following characters:
\302\240
Can someone explain what these characters mean. Is it ASCII format? I need to trim those characters from a file.
I am doing the following:
tr -d '\302\240'
---------- Post updated at 08:35 PM ---------- Previous... (1 Reply)
Hi all,
I was wondering how can i see the special characters like \t, \n or anything else in a file by using Nano or any other linux command like less, more etc (6 Replies)
i need to replace the any special characters with escape characters like below.
test!=123-> test\!\=123
!@#$%^&*()-= to be replaced by
\!\@\#\$\%\^\&\*\(\)\-\= (8 Replies)
Hello all, I'm writing an expect script that will connect to an IMAP server and issue IMAP commands. The problem is that some of the text I need to send includes "quotes" and also !@#$%^&* special characters.
For example, my password is VFR$5tgb but I cannot "send" this because Expect doesn't... (2 Replies)
Hi,
I have written a unix expect utility "ssh-login.exp" which connects (ssh) to remote host and execute some shell script. I am calling this "ssh-login.exp" utility from another shell script.
"ssh-login.exp" takes username, password, host and shell script path to execute on remote host. All... (1 Reply)
Hi,
I have written a unix expect utility "ssh-login.exp" which connects (ssh) to remote host and execute some shell script. I am calling this "ssh-login.exp" utility from another shell script.
"ssh-login.exp" takes username, password, host and shell script path to execute on remote host. All... (1 Reply)
Discussion started by: Mahesh Desai
1 Replies
LEARN ABOUT CENTOS
ibdm-topo-file
IBDM-TOPO-FILE(1) IB DATA MODEL PACKAGE IBDM-TOPO-FILE(1)NAME
IBDM Topology File
The topology file describes the IB connectivity and systems included in the network. It serves two purposes:
1. Support for arbitrary system names to be later used in every report that IBDM generates.
2. Connectivity verification: The specified network topology is verified against the discovered one. Mismatch errors resulting from missing
cables and/or wrong connections are reported by IBADM.
The topology file is composed "system" sections. Each such section describes the connectivity of one system to other systems in the net-
work. The first line of each section is a declaration of the system composed of a system-type, its system-name section, and optional con-
figuration details. The lines to follow until the next empty line describe the connections between this system ports to the other systems.
The following is a formal definition of a system section syntax.
An example is listed afterwards.
SYSTEM-TYPE SYSTEM-NAME [CFG: <b1>=<modifier>, [<b2>=<modifier>]...]
LOCAL-PORT-PANEL-NAME -> REM-SYS-TYPE REM-SYS-NAME REM-PORT-PANEL-NAME
LOCAL-PORT-PANEL-NAME -> REM-SYS-TYPE REM-SYS-NAME REM-PORT-PANEL-NAME
LOCAL-PORT-PANEL-NAME -> REM-SYS-TYPE REM-SYS-NAME REM-PORT-PANEL-NAME
. . .
SYSTEM-TYPE SYSTEM-NAME [CFG: <b1>=<modifier>, [<b2>=<modifier>]...]
LOCAL-PORT-PANEL-NAME -> REM-SYS-TYPE REM-SYS-NAME REM-PORT-PANEL-NAME
LOCAL-PORT-PANEL-NAME -> REM-SYS-TYPE REM-SYS-NAME REM-PORT-PANEL-NAME
. . .
. . .
Where:
SYSTEM-TYPE and REM-SYS-TYPE
Any system that has a corresponding IBNL definition. See man ibdm-ibnl-file
SYSTEM-NAME
The name of the system described in this topology file section.
LOCAL-PORT-PANEL-NAME
The name of the local system port. The numbers printed on the front panel are used together with Ln for Leaf no. N or Sn for Spine no.
N.
REM-SYS-NAME
The name of the system connected to the local port.
REM-PORT-PANEL-NAME
A name of the remote system port. We use the numbers as printed on the front panel and Ln for Leaf number N or Sn for Spine number N.
EXAMPLE
The following is a topology file for a simple cluster with one 24 port switch and two HCAs. The firts HCA named H-1 and connect to the fab-
ric with its two ports. The second HCA named H-2. The switch is of type MTS2400 and is named S-1
MTS2400 S-1
P1 -> MT23108 H-1 P1
P2 -> MT23108 H-1 P2
P24 -> MT23108 H-2 P1
OPTIONAL CFG SECTION
This section in the system declaration line describes the special customization of each board of the system.
That is the CFG string is a set of comma-separated sub-fields. Each sub-field describes some special configuration of a corresponding sys-
tem board. The actual semantics of the specific board modifiers is defined by the IBNL of the specific system.
EXAMPLE
The following is an example of a definition-line in a topology file of the MTS9600 switch system. This switch system can have up to eight
leafs and four spines. This example of the MTS9600 lacks (R) leafs no.6,7 and 8, and lacks spines no. 3 and 4.
MTS9600 PartialGz1 CFG: leaf3=R,leaf5=R,leaf7=R,spine1=R
AUTHOR
Eitan Zahavi, Mellanox Technologies LTD, eitan@mellanox.co.il
IBDM 1.0 2008-06-16 IBDM-TOPO-FILE(1)