05-19-2008
Add $! to the error message to find out why it's dying. Also check your spelling of "localhost".
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower.
What i mean to say is since the send() function in the server program (it is... (2 Replies)
Discussion started by: rajesh_puru
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies
3. UNIX for Advanced & Expert Users
Hi Experts,
need help about release or refresh TCP Connection:
i have the sample like below :
application log connection:
0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00
0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Discussion started by: bucci
3 Replies
4. Programming
Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies
5. Solaris
Hello,
Actually there are some bugs in application which does not close the TCP connection to other server though CORBA.
We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED
Is there any... (4 Replies)
Discussion started by: GIC1986
4 Replies
6. UNIX for Dummies Questions & Answers
Dear experts,
I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers.
How can I pin point what connection failed and what are the ports involved?
Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"?
... (2 Replies)
Discussion started by: cache51
2 Replies
7. IP Networking
Why this happens?
How to solve this?
$netstat -na |grep 9325
tcp 0 0 127.0.0.1:9325 127.0.0.1:9325 ESTABLISHED
When a client socket repeatedly tries to connect to an inactive(no server socket is listening on this port) local port,connect succeeds.
... (1 Reply)
Discussion started by: johnbach
1 Replies
8. Solaris
Hi,
I use solaris Unix .
I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740
root@XX # netstat -an | grep CLOSE_WAIT | wc -l
285
root@XX # netstat -an | grep CLOSE_WAIT
10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies
9. Programming
Hi.
I am writing client - server application using TCP sockets.
I need some very basic functionality, namely: how to check if another "participant" of the connection is still present?
I want to handle situations, when client is gone, or server breaks down, etc. (25 Replies)
Discussion started by: Shang
25 Replies
10. UNIX for Dummies Questions & Answers
I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies
LEARN ABOUT DEBIAN
acheck
ACHECK.1(1) User Contributed Perl Documentation ACHECK.1(1)
NAME
acheck - Check common localization mistakes
SYNOPSIS
acheck [OPTIONS] [INPUT_FILE]
DESCRIPTION
This program parses a file checking for syntax rules and optionally asking Aspell for checking word spelling. It makes fix suggestions and
outputs a corrected file accordingly adding review comments if requested.
It tries to find the file type according to the extension or the first lines and loads rules accordingly.
It displays lines when they are parse.
When an error is found, a menu is displayed. Just press Enter if you don't want to change anything. If a choice suits you, enter the corre-
sponding number. If you want to fix it but no choice is correct, enter a space, then you will be asked for a string to replace the high-
lighted text. The script will replace the highlighted text with your choice and parse it again for new errors.
Here are all the available commands:
Enter, ignore.
Ignore.
Ctrl+L, redraw.
Rewrite the last line, suggestions and hints.
Space, edit.
Edit the highlighted text.
E, edit line.
Edit the whole line.
H, add hint.
Add the displayed hint as review comment. Use this if you want the translator to see the corresponding warning or error but you have no
correction.
N, next line.
Skip the rest of this line.
X, exit and discard all changes.
Quit without saving modifications, the script ask you for confirmation, you have to enter `yes' to exit otherwise parsing starts again
at the current mistake.
a, add in dictionary.
Add the highlighted word to you personal dictionary, capitalized as it is.
l, add lowercase in dictionary.
Lowercase the highlighted word to add it to your personal dictionary.
i, ignore word.
Ignore the highlighted word, same as Enter.
I, ignore all.
Ignore the highlighted word and add it to your session dictionary.
OPTIONS
Verbosity level:
-q, --quiet
quiet mode.
-v verbose, start at level $Debug + 1, add more for more verbosity (see below).
--verbose n
set verbosity level to n (see below).
Files:
-i, --input
input filename, can be '-' to read data from standard input.
-o, --output
output filename, can be '-' to write data to standard ouput. If no output filename is provided, input file is backed up with `bak_ext'
extension and input filename is used.
Spell check:
-s, --spell
check spelling with Aspell.
-d language, --dict language
use language dictionary for Aspell.
-n, --nospell
don't check spelling.
Mode:
-r, --review
review mode, add comments on lines beginning with $Comment after parsed line.
-t, --trans
translator mode, don't add comments, just fix errors.
others:
--rules ruleset
use ruleset rules set.
--type filetype
use filetype whatever the file type is.
--dump
Dump the rules to check and exit, use this for debugging purposes.
-V, --version
print version and exit.
-h, --help
print a short usage message and exit.
Verbosity Level
0 quiet, normal
only warnings and errors
1 debug
names of subroutines
2 debug verbose
names and arguments of subroutines
3 .. 5 debug very verbose
output parsing and checking details
SEE ALSO
acheck(5), acheck-rules(5)
AUTHOR
Nicolas Bertolissio <bertol@debian.org>
perl v5.8.4 2003-10-05 ACHECK.1(1)