Questions[console](server)

I've seen this with so many consoles (on Linux, Mac, ...), and with lots of different machines in many different networks. I can never pinpoint the exact reason, why this happens: All you have to do is log in to a machine via SSH. If the connection breaks for some reason (for simplicity, let's say the network cable was pulled), then sometimes the console just hangs forever - at other times, it just exits fine to the parent shell.

It's so annoying when this happens (e.g. you lose the command history.) Is there maybe a secret keyboard shortcut which can force an exit (Ctrl-C or Ctrl-D don't work)? And what's the reason for this random "bug" across all the implementations anyway?

I need it to determine if hitting ctrl+d would disconnect me from server or just close current screen.

Is it somehow possible to check if I'm right now in screen session?

I'm on MacOSX, I did ln -s on a directory and these are the results:

-rwxrwxr-x@ 1 shiki  admin   970332 Mar  6 16:38 apc.so
-rwxrwxr-x@ 1 shiki  admin   653884 Mar  6 16:38 eaccelerator.so
-rw-rw-r--@ 1 shiki  admin    60064 Mar  6 16:38 gettext.a
-rwxrwxr-x@ 1 shiki  admin    80320 Mar  6 16:38 gettext.so
-rw-rw-r--@ 1 shiki  admin   514784 Mar  6 16:38 imap.a
-rwxrwxr-x@ 1 shiki  admin  3886132 Mar  6 16:38 imap.so

What do those @ symbols mean?

I've got an Ubuntu server that boots up in text mode. It rarely has a screen or keyboard attached to it, but when I do attach a screen, I usually have to attach a keyboard too, because the darn console mode screen saver will be on and I'll need to hit a key to see what's going on.

I'm aware that the setterm command can disable this, but it's a per-session thing. How can I make it so the machine never ever blanks the screen in text mode, even when it's first booted up and sitting at the login prompt?

Is there a way to remote tail 2 files?

I have two servers(a and b) behind a load balancer and I would like to do something like this if possible:

tail -f admin@serverA:~/mylogs/log admin@serverB:~/mylogs/log

Thanks!