|
Grex > Oldcoop > #315: VOTE PROPOSAL: Remove the idle daemon. | |
|
| Author |
Message |
| 25 new of 88 responses total. |
remmers
|
|
response 50 of 88:
| 
Feb 24 16:22 UTC 2006 |
That script has been around forever. Like I said in #47, an
idled-defeater is trivial to implement.
|
richard
|
|
response 51 of 88:
|
Feb 24 16:59 UTC 2006 |
I think the idle zapper should stay because when a user is logged in and his
computer crashes or he otherwise becomes a ghost, that ghost login won't go
away unless its zapped. you could run a !who and see a zillion ghost logins
because nobody on staff logged in to manually clean up the mess.
|
cross
|
|
response 52 of 88:
|
Feb 24 17:13 UTC 2006 |
Normally, those `ghost' logins go away by themselves once the network notices
that the connection is gone. Let's try this and see what happens. If it's
a problem, we can act accordingly.
|
scholar
|
|
response 53 of 88:
|
Feb 24 17:26 UTC 2006 |
Re. 50: :(
|
remmers
|
|
response 54 of 88:
|
Feb 26 02:44 UTC 2006 |
Re ghost logins - they don't seem to be accumulating. I ran a small
experiment: Logged in, put my computer to sleep (thus losing the
network connection), came back a few hours later. I was no longer
connected. Logged in on another terminal; my previous login was gone.
So the system seems to be taking care of them.
|
cross
|
|
response 55 of 88:
|
Mar 2 21:49 UTC 2006 |
Well, Idled has been off for a week now, and so far, nothing particularly
bad seems to be happening. At my count a few minutes ago, about 13 logins
that would have been zapped are logged in. Most of those have been idle
for less than 3 hours. The ability to be logged in from more than one
terminal is convenient.
|
cross
|
|
response 56 of 88:
|
Mar 23 17:06 UTC 2006 |
Today marks four weeks since John Remmers turned off idled. I don't think
there have been any major system problems; one person complained about lack
of a TTY device on login, but I note that the upper limit for tty's seems
pretty low right now (somewhere in the 40's). It seems that that limit
should be increased, rather than bring back idled.
As of right now, grex claims to have 45 users logged in. At least two of
those are doing something with FTP; the rest are doing whatever it is that
people do on grex. Of those, around half have been idle long enough that
they would have been zapped. But, only about 7 have been idle longer than
3 hours. If we assume that some people go to sleep, wake up, and do their
grex thing but just leave an idle shell open most of the time, that doesn't
seem like a bad number.
In my opinion, this experiment has been a success. Other comments?
|
marcvh
|
|
response 57 of 88:
|
Mar 23 17:35 UTC 2006 |
For my own experience, I sometimes grex from work, where we have an
application proxy that is very aggressive about timing out idle
connections. The net result is that if I am distracted even briefly my
connection gets terminated there, but it seems to take Grex a long time
before noticing and removing the session.
The upshot is that it's pretty easy for me to, if I'm not paying
attention, be logged in several times "at once" because the other
connections are no longer open on my end. This isn't a big deal for
me; when I notice I can clean it up. I'm only mentioning it in case
there might be others like me.
|
nharmon
|
|
response 58 of 88:
|
Mar 23 18:43 UTC 2006 |
If it was a big deal, you could kill your other login processes Marc.
|
marcvh
|
|
response 59 of 88:
|
Mar 23 19:05 UTC 2006 |
Um, yes, I'm aware of that, that's why I said I "can clean it up."
Thanks.
|
nharmon
|
|
response 60 of 88:
|
Mar 23 21:08 UTC 2006 |
Do you run screen?
|
tod
|
|
response 61 of 88:
|
Mar 23 21:45 UTC 2006 |
I wasn't able to log in on Tuesday night due to used up tty's.
|
naftee
|
|
response 62 of 88:
|
Mar 23 22:41 UTC 2006 |
isn't tuesday night family time ?!
|
cross
|
|
response 63 of 88:
|
Mar 24 00:00 UTC 2006 |
I'd like to bump up the tty limit and see what happens. It should be higher
anyway....
|
naftee
|
|
response 64 of 88:
|
Mar 24 03:55 UTC 2006 |
i'm sure you do a lot of bumping in those friday night dance clubs, dan
|
cross
|
|
response 65 of 88:
|
Mar 24 06:21 UTC 2006 |
What can I say? Your mom is a freak like that, son.
|
naftee
|
|
response 66 of 88:
|
Mar 24 23:34 UTC 2006 |
you're.... my mom ?!
|
tod
|
|
response 67 of 88:
|
Mar 24 23:56 UTC 2006 |
And that wasn't breast milk, soup
|
naftee
|
|
response 68 of 88:
|
Mar 25 04:37 UTC 2006 |
oh my.
that's why they told me milk is yellow
|
kingjon
|
|
response 69 of 88:
|
Mar 29 00:43 UTC 2006 |
I'm getting "all network ports in use" errors when I try to telnet in.
(Ssh was just sitting there, so I tried telnet to confirm my
suspicion; this was posted via backtalk.)
|
cross
|
|
response 70 of 88:
|
Mar 29 03:47 UTC 2006 |
All network ports, or all terminals? The two are rather different. At
present, there are only about 42 people logged in, so I don't think it's
the latter.
Possibly, if grex is serving a lot of network requests (mail, the web
server, etc) it can run out of endpoints for TCP connections, which would
make telnet not work (nor SSH, for that matter) though that's rather
different than running out of pseudo-terminals, which would be the case
if there were too many idle logins, as you seem to be implying.
|
spooked
|
|
response 71 of 88:
|
Mar 29 09:04 UTC 2006 |
And, it is near impossible for grex to run out of the former (unless we
are being DoS attacked).
|
kingjon
|
|
response 72 of 88:
|
Mar 29 11:15 UTC 2006 |
"All network ports in use" was what telnet said.
|
cross
|
|
response 73 of 88:
|
Mar 29 14:57 UTC 2006 |
Regarding #71; Oh, I don't know about that. I've gotten machines to run
out of TCP PCB's pretty easily, usually by running a benchmark program or
something against it.
Regarding #72; I doubt it had much to do with idle logins, then.
|
kingjon
|
|
response 74 of 88:
|
Mar 29 18:51 UTC 2006 |
I just assumed it was the same problem -- sorry.
|