What was the process? The performance described in the earlier posting1 was accurate.

Certain script functions and processes can trap signals. while loops can run away like crazy.

See:

SSH session drops - Does the command continue executing?

Edit 1 at 4:22PM

From the bash manpage:

The shell exits by default upon receipt of a SIGHUP. Before exiting, an interactive shell resends the SIGHUP to all jobs, running or topped. 

Initial research1 is showing that OpenSSH probably ignores SIGHUP, maybe more signals.

What was the process? The performance described in the earlier posting1 was accurate.

Certain script functions and processes can trap signals. while loops can run away like crazy.

See:

SSH session drops - Does the command continue executing?

Edit 1 at 4:22PM

From the bash manpage:

The shell exits by default upon receipt of a SIGHUP. Before exiting, an interactive shell resends the SIGHUP to all jobs, running or topped. 

Initial research1 is showing that OpenSSH probably ignores SIGHUP, maybe more signals.

What was the process? The performance described in the earlier posting1 was accurate.

Certain script functions and processes can trap signals. while loops can run away like crazy.

See:

SSH session drops - Does the command continue executing?

What was the process? The performance described in the earlier posting1 was accurate.

Certain script functions and processes can trap signals. while loops can run away like crazy.

See:

SSH session drops - Does the command continue executing?

Edit 1 at 4:22PM

From the bash manpage:

The shell exits by default upon receipt of a SIGHUP. Before exiting, an interactive shell resends the SIGHUP to all jobs, running or topped. 

Initial research1 is showing that OpenSSH probably ignores SIGHUP, maybe more signals.