You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the hub is restarted suddenly either because of power failure or some other reasons; the entries in user logs table isn't updated. So, if a user was connected to the hub before restart, userinfo command displays Still connected more than once. For eg.
(5.0)_Sinister™
| IP History:
| 10.*.*.* From: 2013-06-14 05:59:10 To: Still connected
| 10.*.*.* From: 2013-06-13 14:44:57 To: Still connected
| 10.*.*.* From: 2013-06-13 12:26:21 To: 2013-06-13 14:43:03
| 10.*.*.* From: 2013-06-13 10:22:45 To: 2013-06-13 12:24:36
| 10.*.*.* From: 2013-06-12 21:56:45 To: 2013-06-13 10:20:49
GTX_465
| IP History:
| 10.*.*.* From: 2013-06-14 16:07:22 To: Still connected
| 10.*.*.* From: 2013-06-14 11:35:57 To: 2013-06-14 16:03:39
| 10.*.*.* From: 2013-06-14 09:30:19 To: 2013-06-14 10:38:29
| 10.*.*.* From: 2013-06-14 09:11:22 To: 2013-06-14 09:29:53
| 10.*.*.* From: 2013-06-13 13:05:20 To: Still connected
| 10.*.*.* From: 2013-06-13 13:02:16 To: 2013-06-13 13:02:22
PS:
The last hub restart was 2013-06-14 05:50:25.
The text was updated successfully, but these errors were encountered:
If the hub is restarted suddenly either because of power failure or some other reasons; the entries in user logs table isn't updated. So, if a user was connected to the hub before restart,
userinfo
command displays Still connected more than once. For eg.(5.0)_Sinister™
GTX_465
PS:
The last hub restart was 2013-06-14 05:50:25.
The text was updated successfully, but these errors were encountered: