... I am changing the subject of this thread, as it is now clear that nterm is only a name attached by nmap to port 1026.
More details on gnome-session in the local machine: --> lsof -i tcp:1026 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME gnome-ses 312 sb 3u inet 304 TCP *:1026 (LISTEN) --> netstat -p | egrep 312 tcp 0 0 localhost:1027 localhost:16001 ESTABLISHED 312/gnome-session unix 1 [ ] STREAM CONNECTED 6844 312/gnome-session @00000047 unix 1 [ ] STREAM CONNECTED 316 312/gnome-session @0000001a unix 1 [ ] STREAM CONNECTED 6135 312/gnome-session /tmp/.ICE-unix/312 unix 1 [ ] STREAM CONNECTED 992 312/gnome-session /tmp/.ICE-unix/312 unix 1 [ ] STREAM CONNECTED 499 312/gnome-session /tmp/.ICE-unix/312 unix 1 [ ] STREAM CONNECTED 484 312/gnome-session /tmp/.ICE-unix/312 unix 1 [ ] STREAM CONNECTED 358 312/gnome-session /tmp/.ICE-unix/312 unix 1 [ ] STREAM CONNECTED 327 312/gnome-session /tmp/.ICE-unix/312 --> ps ax | egrep 312 312 ? S 0:00 /usr/bin/gnome-session --purge-delay=15000 1671 pts/1 S 0:00 egrep 312 gnome-session is started by gdm. The relevant files are /gdm/Session/Gnome /gdm/Session/Default gnome-session does not have a man page, but has a --help command line option. The only DOCUMENTED option concerning tcp listening is --espeaker, that specifies the port of ... the sound server. Thank goodness they did not put my mouse as a tcp service! (sorry for the sarcasm) Sergio
