Is it bad to be constantly connected to a host...

[gopunk]

i ssh into all these different hosts here at work.. but because i'm lazy, when i go home, i simply lock my computer, leaving all my terminal windows open. is this detrimental for the hosts? or am i fine... i've been doing this for a while and they haven't crashed any more than usual, so i'm guessing this isn't too bad, but i wanted y'all's opinion on this... thanks!

 

[MercenaryForHire]

Unless they've got a limit of 5 max connections (or something else low) and no idle-timeout (are you still logged on in the morning?) then it's not really much of an issue. Unless someone "h4x0rs" your work computer and then "0wnz" all your SSH sessions.

- M4H

 

[gopunk]

Originally posted by: MercenaryForHire
Unless they've got a limit of 5 max connections (or something else low) and no idle-timeout (are you still logged on in the morning?) then it's not really much of an issue. Unless someone "h4x0rs" your work computer and then "0wnz" all your SSH sessions.

- M4H

i'm pretty sure there isn't a low limit, and no idle timeout (i'm still on in the morning). but every once in a while (maybe once every 1.5 months), i get something like this when i come in:

Broadcast message from root@lists (tty) at 21:20:19 ...

PLEASE LOG OFF NOW ! ! !
System maintenance in progress.
All processes will be killed now.




Broadcast message from root@lists (pts/2) at 21:20:19 ...

! ! ! SYSTEM BEING BROUGHT DOWN NOW ! ! !

Command terminated on signal 9.

then inevitably i can't log back in because ssh wasn't able to start up properly or some crap like that. not sure if that is my fault or not

 

[Entity]

Damnit, so you're the one slowing dante down!

Nah, I do the same thing.

Rob

 

[Scarpozzi]

Some people may argue that it's more secure to stay logged in because that's less times you pass your authentication to the server...even if it is encrypted.

I doubt it's much load on the host as long as they have a decent system with a decent connection.

 

[MercenaryForHire]

Naw, not your fault. They just want to shut the host down for a bit. If you were the only one online, they'd check, see that you hadn't done squat for a few hours, and reboot anyhow with no broadcast messages.

If you are doing something though, please pay attention to the messages. I hate fielding calls from clueless users who've had a half-hour warning to get off the damn server.

- M4H

 

[wyvrn]

Usually those messages are sent when the system comes down for maintenance or full backups. Since you are logged in, you get to see the messages. Users that close their connections don't see them. As far as reconnecting, you might have to stop and restart your ssh service if it terminated abnormally?

Originally posted by: gopunk

Originally posted by: MercenaryForHire
Unless they've got a limit of 5 max connections (or something else low) and no idle-timeout (are you still logged on in the morning?) then it's not really much of an issue. Unless someone "h4x0rs" your work computer and then "0wnz" all your SSH sessions.

- M4H

i'm pretty sure there isn't a low limit, and no idle timeout (i'm still on in the morning). but every once in a while (maybe once every 1.5 months), i get something like this when i come in:

Broadcast message from root@lists (tty) at 21:20:19 ...

PLEASE LOG OFF NOW ! ! !
System maintenance in progress.
All processes will be killed now.




Broadcast message from root@lists (pts/2) at 21:20:19 ...

! ! ! SYSTEM BEING BROUGHT DOWN NOW ! ! !

Command terminated on signal 9.

then inevitably i can't log back in because ssh wasn't able to start up properly or some crap like that. not sure if that is my fault or not

 

[gopunk]

entity - yup, it's me


alright thanks guys, i'll keep on being lazy then i only see this stuff when i come in... these are production machines so they only time they would ever get taken down is at night when traffic is small