Afraid to log off server...

Pho3nix

The Legend
Joined
Jul 31, 2009
Messages
32,825
Reaction score
3,033
Location
On the toilet
Hi all,

Am I the only person who is mildly worried of logging off a remote session after finishing work on a server?
Accidentally turned off a production server when I was an intern many moons ago but haven't gotten over it.

Is it bad form to just close the window and leave the user logged in?

:cry::(
 
Last edited:
Hi all,

Am I the only person who is mildly worried of logging of a remote session after finishing work on a server?
Accidentally turned off a production server when I was an intern many moons ago but haven't gotten over it.

Is it bad form to just close the window and leave the user logged in?

:cry::(

Check with the IT department or responsible person(s), privileges are wrong, someone should secure the policy groups.

Nothing wrong with logging out... depends on your user setup :whistle:
 
I've got an extra workstation on which I keep the rdp sessions open and running. Whenever I need to log in either in the office, or remotely, I just need to rdp to that specific PC. Of course all sessions auto-lock after an inactivity timeout, need to re-enter password...
 
I just click the X, no problems whatsoever.
 
Check with the IT department or responsible person(s), privileges are wrong, someone should secure the policy groups.

Nothing wrong with logging out... depends on your user setup :whistle:
LOL possibly true. Still gives me shivers thinking about the k@k I endured after that.
I've got an extra workstation on which I keep the rdp sessions open and running. Whenever I need to log in either in the office, or remotely, I just need to rdp to that specific PC. Of course all sessions auto-lock after an inactivity timeout, need to re-enter password...
Hope that's the case with this server :)
I just click the X, no problems whatsoever.
:cool:

Seriously though, is there any hard in leaving the session on with a simple click on the X. Resource or otherwise?
 
When you just close it you keep a license hostage and if there are no more licenses available other people can no longer log in.

Just log out and read the the messages before just clicking OK.
 
LOL @ OP! I know your pain.

Once upon a time, many many moons ago whilst I was working at CareerJunction, I made the noob mistake of sending a command for one terminal window to all using Cluster SSH.

The command which was meant to clean old builds clogging up space on the servers was:

"rm -rf *" :D

This all was done at 12:46 (peak time back then) - I am convinced I set a record deployment time on that day! I narrowly escaped disciplinary action.
 
Also, do not change the firewall rules to block all logins and the log out. :)
 
Hi all,

Am I the only person who is mildly worried of logging off a remote session after finishing work on a server?
Accidentally turned off a production server when I was an intern many moons ago but haven't gotten over it.

Is it bad form to just close the window and leave the user logged in?

:cry::(

Depends on windows task scheduler.

The only time I feared a shutdown was when I was working on SQL and someone shutdown the server without asking and corrupted the DB.
 
Two things also spring to mind:

1. Logging off a Linux box after you have disabled ssh password authentication.
2. Any updates to any server, especially Windows servers.
 
It depends. Sometimes, I logoff, sometimes I close the rdp window. I'd say there is no harm in either. It just depends on your policies.
 
Get your IT dept to lock up those permission's, only domain admin and above level accounts should have permissions to shutdown servers.
 
Think we have all at some point done a similar mistake. I once disabled an ethernet connection on production server. Had to quickly drive across town to go and fix it. Luckily it wash't a major PITA - but lesson learnt.

As with logging out - I really see no issues with that.
 
When you just close it you keep a license hostage and if there are no more licenses available other people can no longer log in.

Just log out and read the the messages before just clicking OK.

This. Experienced this many times before.
 
"Accidently"? ;)

Lol, ye. Accidentally because I wasn't thinking, disk was running out of space and found these files which were taking up space :D

I must say I was surprised as the Windows Server guest still booted up but there were some very strange side effects.
 
Get your IT dept to lock up those permission's, only domain admin and above level accounts should have permissions to shutdown servers.

Just checked and the accounts we use to log onto the servers are Admin accounts so we don't have to log requests with IT. Thus the risk of shut-downs :(
 
Top
Sign up to the MyBroadband newsletter
X