looking for equiv. of BSDetclogin.conf file to supress login timeouts
Black Sun and said:
This happens. AFAICT, it's because of keepalive packets not going through, or possibly the cablemodem dropping connections that have been idle for more than N minutes. It's not just incoming connections either; I've had this happen when sshed in to the computers at ork, which have static IPs, no evil cable monopoly controlling connectivity, and all that jazz.
This is a red herring. You should look inetc-ssh-sshdconfig on your home machine and make sure that "TCPKeepAlive yes" is set. This should be yes by default, though. You should also check the man pages for sshconfig and sshdconfig for the ClientAliveInterval and ServerAliveInterval options.
What worked better for me is to put a fragment like so in ~-bin-keepalive.sh :
Now that I have my file server running (well, it boots and stays up until I shut it down), I'd like to find tools equivalent to the ones I...
#!-bin-bash while true ; do echo "..." sleep 300 done
...and when I know I'm going to be idle for a while, execute keepalive.sh . The I-O every 5 minutes seems to keep everything alive without a problem.
You might like "mc", the Midnight Commander aka Mouseless Commander program, which was originally inspired by (if memory serves) one...
Also, remember that running a server of any type on a non-"business clbutt" cablemodem is probably not allowed under the letter of Comcast's TOS. sshd wouldn't bug them much, but apache or Postfix or ftpd probably would.
-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL