Fixed: Explicitly close socket on exit instead of relying on os to do it

Server may have to wait additionally to detect that client is gone and good practice to clean up resources as soon as possible.

https://unix.stackexchange.com/questions/386536/when-how-does-linux-decides-to-close-a-socket-on-application-kill

https://stackoverflow.com/questions/54053329/why-does-a-client-not-close-its-socket

Author: agnostic-apollo

termux-am.cpp

@@ -101,13 +101,15 @@ int main(int argc, char* argv[]) {
         memset(tmp, '\0', sizeof(tmp));
         if (! recv_part(fd, tmp, sizeof(tmp)-1)) {
             fputs("Exit code too long", stderr);
-            exit(1);
+            close(fd);
+            return 1;
         }
         errno = 0;
         exit_code = strtol(tmp, NULL, 10);
         if (errno != 0) {
             perror("Exit code not a valid number");
-            exit(1);
+            close(fd);
+            return 1;
         }
     }
 
@@ -131,5 +133,7 @@ int main(int argc, char* argv[]) {
         } while (!ret);
     }
 
+    close(fd);
+
     return exit_code;
 }