- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- how to capture the signal of interrupt connecting ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 07:42 PM
тАО10-13-2008 07:42 PM
how to capture the signal of interrupt connecting Socket?
I have writen client socket by C language connect to socket server order to tranfer file between them (Socket client running on HP-UX). But I have got a problem, socket server somtime disconnect from session but I don't capture the signal of interrupt session to resume transfer file session when client connect again.
Plz help me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 09:33 PM
тАО10-13-2008 09:33 PM
Re: how to capture the signal of interrupt connecting Socket?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 11:22 PM
тАО10-13-2008 11:22 PM
Re: how to capture the signal of interrupt connecting Socket?
Nomally, Client and Server socket transfer data each other. When have a problem, ex: Socket Server had been power suddenly shutdown or Socket server hang...I must fransfer file from first. I want write pointer of file (I write a C program read a file and the file is read fransfer from client to server) to other file before client socket closed. But I can't do it, plz help me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2008 04:44 PM
тАО10-14-2008 04:44 PM
Re: how to capture the signal of interrupt connecting Socket?
That could take the form of periodic "I have gotten as far as N" messages back the other way on the connection.
Perhaps it could take the form of the client saying "how large is this file" and the server saying it is N bytes in size and the client deciding to start transferring from N. That would probably have to be coupled with the client only using that mechanism on a reconnect after disconnect and not on an initial connect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-16-2008 12:25 AM
тАО10-16-2008 12:25 AM
Re: how to capture the signal of interrupt connecting Socket?
2) The connection is reset when:
- there is unsent data, and retransmissions failed. retransmission will last for tcp_ip_abort_interval (ndd tunable 10 min/default). Retransmission may stop also if peer system reset the connection - after a reboot for instance.
3) disconnection on read() side is detected if we receive a reset. If connectivity is completely lost, only keepalive option may help to detect the problem.
by default keepalive is not set, and keepalive interval is 2 hours.
- so you may reduce the interval to detect it sooner - don't set abort interval to a too low value.
Else only your protocol can help you on identifying sooner connectivity is lost and where.
for instance, send an ack every 128k with a timeout, So you know where to start over.