I have a server computer and a client computer.
The client computer processing information from server computer and running operation. Server computer gave commands to client computer to control its operation.

Server and client computer are connected using wireless network.

We have programmed the client computer to continue the operations set even when the wireless network terminated or disconnected (with the condition that the server computer program still active) until the operation is complete or it receive other commands.

The client computer will continuously search for reconnecting the network itself. The server and client computer network through wireless can be connected back without interrupting client computer's current operation until the server computer is giving another command as server and client computer are sharing the same ip address and port number.

The problem now is

when the server computer program is closed or shut down, the client computer and server computer can no longer automatically or manually connected to each other without first terminating the client's ongoing operations.

When we attempt to connect the client computer back to server computer, it is not successful. This is due to the server computer can no longer use the same port number that the client computer is using as it is not allowed. We need to terminate the client computer operation and establish connection between them first. Then, only we can start our work from the beginning.

How can we solve this? How to make the client computer continue running on its own following the preset operation and without interrupting the client computer operation, connect the server and client back using the same ip address and port number?

Hi eryn,

Please correct me if I'm wrong but you mentioned the server and client are sharing the same ip address ?? .. this may cause you some trouble as 2 hosts on the same network need to have unique addresses.

Assuming you get the addressing sorted out.. one of the simplest ways to kick off a job on one host from another is to install 'screen'. The process to use screen looks like this:

1. ssh from host_a to host_b
2. run 'screen'
3. run the command you desire, backgrounding is not necessary
3. press '[ctrl]+A D' to detach from the screen session
4. logout

To check on the job later:

1. ssh from host_a to host_b
2. run 'screen -ls' to list your screen sessions ( you may have more than 1)
3. run 'screen -r' or 'screen -r session' to reconnect
4. exit or detach again depending on job status

cheers

kbp

Hi kbp,

Maybe I am not explaining clear enough.
Actually, the client computer and the server computer on their own has a unique ip address.
The client computer will 'telnet' to the server computer using the server computer ip address to connect.

We have a chat window in the server computer to give command.
When this chat window is closed, the connection between client and server is terminated.
The client computer suppose to continue running all the command written in program.
However, it will hang at the last command it executes. For example, if the last command it is running before the chat window is closed is turning motor CW, then it will turn non stop until we cut off the cable connection between the motherboard and the Bus system.

When we reopen the chat window and try to connect back to the client computer, we are not allowed to do so. The error message shown said that the port number already in used and each port number can only be used by one people, thus we cannot connect.

Well, my colleague just found out the solution.
It is just a very minor change.

When the chat window is closed, a value of 0 is return to the program.
In our program, in order to connect back the operation, we put the condition as
(returnresult<0)

Therefore, the command underneath this condition can never be executed.

Thus, we have change the condition to (returnresult<=0)

Anyway, thank you kbp.