![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Mike Bilow wrote: > > Actually, ssh usually exchanges periodic "keepalive" packets to detect if > the other end has gone away. If the ipchains timeout is set long enough, > the ssh keepalive packets should prevent a timeout even if nothing happens > in the tail or top windows. This was a very timely discussion. Unfortunately, not quite timely enough to prevent me from almost hanging my server. I ssh'd from my laptop to my office's Linux server. I changed something trivial in my backup script, and ran it to make sure it was o.k. It started runnning, but a half hour or so later, people started having problems mounting Samba shares, DNS stopped working, etc. So I sat down at the server console, and I couldn't even log in. Couldn't use ssh to get in either. I was contemplating hitting the power switch (ouch), but tried turning off the tape drive first. Presto. Everything came back. Yikes. -Ron- - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |