Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Special characters automatically gets returned - Red Hat Enterprise Linux Server release 7.0 Post 302944084 by bakunin on Friday 15th of May 2015 09:54:05 AM
Old 05-15-2015
As stated there this thread is neither closed nor moved.

If you have valuable information pertaining your problem state it here.

As per the threads problem: it looks like a prompt of some sort. Investigate the setting of "PROMPT_COMMAND" and "PS1", "PS2", "PS3" and "PS4".

My suspicion is that you put some configuration into a "~/.profile" (where it doesn't belong to at all) instead of a "~/.bashrc" and this is coming back to you now. But without a better description of your problem and the respective data this is just a wild guess.

I hope this helps.

bakunin

Moderator's Comments:
Mod Comment Oh, and by the way:

Quote:
We need urgent solution for us
This is clearly YOUR problem, not ours. If you need a reliable and responsive support then, by all means, HIRE SOMEONE! The service here is offered on an as-is-basis. We are not obligated to do anything, much less to doing it in a certain time.
 

2 More Discussions You Might Find Interesting

1. Red Hat

To download mod_ssl for Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga)

Hi, Anyone know how and where to download mod_ssl package into Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga) ? could you also show what's the procedure to apply the mod_ssl into the server and how to apply the digital cert into apache server and so on. Thanks. (1 Reply)
Discussion started by: ckwan
1 Replies

2. Red Hat

Special characters automatically gets returned - Red Hat Enterprise Linux Server release 7.0

Dear experts, We are using Linux OS i.e Red Hat Enterprise Linux Server release 7.0 I log to the server using putty & default shell is Code: -bash4.2$ echo $SHELL /bin/bash special character automatically gets returned in my putty. Code: -bash-4.2$ ~ Also this... (0 Replies)
Discussion started by: dba1981
0 Replies
TCPCLI(1)							  BP executables							 TCPCLI(1)

NAME
tcpcli - DTN TCPCL-compliant convergence layer input task SYNOPSIS
tcpcli local_hostname[:local_port_nbr] DESCRIPTION
tcpcli is a background "daemon" task comprising 1 + N threads: one that handles TCP connections from remote tcpclo tasks, spawning sockets for data reception from those tasks, plus one input thread for each spawned socket to handle data reception over that socket. The connection thread simply accepts connections on a TCP socket bound to local_hostname and local_port_nbr and spawns reception threads. The default value for local_port_nbr, if omitted, is 4556. Each time a connection is established, the end-points will first exchange contact headers, because connection parameters need to be negotiated. tcpcli records the acknowledgement flags, reactive fragmentation flag and negative acknowledgements flag in the contact header it receives from its peer tcpclo task. Each reception thread receives bundles over the associated connected socket. Each bundle received on the connection is preceded by message type, fragmentation flags, and size represented as an SDNV. The received bundles are passed to the bundle protocol agent on the local ION node. tcpcli is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol; the text of the command that is used to spawn the task must be provided at the time the "tcp" convergence layer protocol is added to the BP database. The convergence layer input task is terminated by bpadmin in response to an 'x' (STOP) command. tcpcli can also be spawned and terminated in response to START and STOP commands that pertain specifically to the TCP convergence layer protocol. EXIT STATUS
0 tcpcli terminated normally, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem identified in the log file and use bpadmin to restart tcpcli. 1 tcpcli terminated abnormally, for reasons noted in the ion.log file. Investigate and solve the problem identified in the log file, then use bpadmin to restart tcpcli. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: tcpcli can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No such tcp duct. No TCP induct matching local_hostname and local_port_nbr has been added to the BP database. Use bpadmin to stop the TCP convergence- layer protocol, add the induct, and then restart the TCP protocol. CLI task is already started for this duct. Redundant initiation of tcpcli. Can't get IP address for host Operating system error. Check errtext, correct problem, and restart TCP. Can't open TCP socket Operating system error. Check errtext, correct problem, and restart TCP. Can't initialize socket Operating system error. Check errtext, correct problem, and restart TCP. tcpcli can't create access thread Operating system error. Check errtext, correct problem, and restart TCP. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), tcpclo(1) perl v5.14.2 2012-05-25 TCPCLI(1)
All times are GMT -4. The time now is 03:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy