|
Grex > Coop8 > #53: Adding something like "watch" to Grex | |
|
| Author |
Message |
| 25 new of 64 responses total. |
steve
|
|
response 25 of 64:
| 
Apr 13 04:49 UTC 1996 |
It probably would. It's just that the kill_orphans script would
likely be a bit more busy, killing them when their masters had logged
off.
|
ajax
|
|
response 26 of 64:
|
Apr 13 05:39 UTC 1996 |
I think the solution Jan had for that, making the program aware of when
its owner disappeared, would make that a non-issue. It's not an inherant
problem of all watch programs, just some implementations.
|
janc
|
|
response 27 of 64:
|
Apr 13 05:59 UTC 1996 |
I put a version of the watch program I once wrote for M-Net in
/u/janc/bin/watch. You can give it a list of user names on the command line
and it will watch for those. If you give no arguments, it watchs everyone
(amazingly obnoxious with the number of people using Grex). A -s turns off
bells. Theoretically this should exit when you log off. I haven't tested
this thoroughly. I guess there is no reason this couldn't be put in
/usr/local/bin, except that I dislike it and don't want to be saddled with
maintaining it. Source is in /u/janc/src/watch.c. There is no man page.
|
steve
|
|
response 28 of 64:
|
Apr 13 12:09 UTC 1996 |
Good show Jan. I'll play with it and see how it goes. I think that
if it work at all it will just work and we can be done with it. Someone
who likes writing in that awful roff format could write a page for it,
I suppose.
|
arthurp
|
|
response 29 of 64:
|
Apr 13 21:00 UTC 1996 |
I have been using it for a couple days, and going back and forth between
myself and my pseudo to make sure it is going away after I log out. It does
not go away instantly, but it has (so far) always gone away in about 1-2
minutes. I have not been watching the time to see if this is a coincidence
with the orphan-killer, or if watch really works as expected. So far so good.
|
slynne
|
|
response 30 of 64:
|
Apr 13 21:01 UTC 1996 |
Just my two cents worth...
I really like using the watch program on Mnet because there are a few
people I really like talking to and it is nice to know when they come
online. If there were a watch program here, I would use it for the same
reason. I dont mind if folks watch for me. If I want to go incognito, I
will make a pseudo although I cant think of a single reason for folks not
to know if I am online or not at the moment.
|
rcurl
|
|
response 31 of 64:
|
Apr 14 06:24 UTC 1996 |
I turned it on - with the beep. Is there any way to (grrrr!) kill it
without logging off?
|
dang
|
|
response 32 of 64:
|
Apr 14 17:23 UTC 1996 |
If you do a ps-aux | sort | more, you will get a list of all the processes
starting with yours. (That way, you don't need more than one screen of
output...) find watch, and kill it. That's the only way I've been able to
get rid of it.
|
davel
|
|
response 33 of 64:
|
Apr 14 18:37 UTC 1996 |
(Don't forget the blank after the "ps" and before the "-aux".)
|
rcurl
|
|
response 34 of 64:
|
Apr 14 20:27 UTC 1996 |
Thanks, dang - that worked (though the list was just alphabetical by id).
Why doesn't just !ps show it? Isn't it my process? I tried to start watch
in silent mode with !/u/janc/bin/watch -s, but it didn't even start watch.
|
dang
|
|
response 35 of 64:
|
Apr 14 21:38 UTC 1996 |
Well, watch runs as a background process, which ps doesn't show by default.
(Sorry, my id is early, so I'm always first. I wondered about that. Maybe
on my other system it does format me first.)
|
davel
|
|
response 36 of 64:
|
Apr 15 11:19 UTC 1996 |
Well, it *shouldn't*, I think. But I wondered a bit at your saying that -
but I always forget the differences between Grex's ps & what I'm more used
to, so I let it pass. My suggestion would be that instead of piping through
sort, you pipe it through fgrep for your username. (With that you won't need
more, either, normally.)
|
remmers
|
|
response 37 of 64:
|
Apr 15 12:33 UTC 1996 |
Or you could skip the piping altogether and just do 'ps -ux'.
|
popcorn
|
|
response 38 of 64:
|
Apr 15 16:51 UTC 1996 |
Interesting... I tried running watch and then "ps -ux", but it didn't show
my watch process. It did, however, claim that I have a defunct process still
running from March 31. And a csh from 2:30am today, when I'd been sound
asleep for 4 hours.
|
popcorn
|
|
response 39 of 64:
|
Apr 15 17:08 UTC 1996 |
Ya know what else is interesting... I ran "/u/janc/bin/watch -s" and it didn't
give me any error messages, but it also doesn't appear to be watching
anything. I haven't seen a single message that someone has logged on or off.
|
popcorn
|
|
response 40 of 64:
|
Apr 15 17:11 UTC 1996 |
Oh -- another way to find out what processes you are running is to find out
what tty you are on (for example, I typed "!tty" to find that I'm on ttyh3)
and then do a "ps -th3" to list all the processes on your tty. (Substitute
the last two characters of your tty number for the h3 there; I used h3 because
I'm on ttyh3).
I did a "/u/janc/bin/watch" without the -s flag, and, Jan is right, running
watch with no parameters *is* amazingly obnoxious with the number of users
that Grex has.
|
dang
|
|
response 41 of 64:
|
Apr 15 21:20 UTC 1996 |
I think the a is necessary to see background processes. At least here at hope
it is. According to our ps manpage, ps -aux | sort should sort for your UID
first, and then the others in alphabetical order.
|
rcurl
|
|
response 42 of 64:
|
Apr 16 01:53 UTC 1996 |
ps -ux worked fine to show my processes, including watch. The question
of the "silence" flag, however, remains unresolved. Where is janc when we
need his silence?
|
popcorn
|
|
response 43 of 64:
|
Apr 16 05:49 UTC 1996 |
Well, he did say he didn't want to have to support the watch program....
|
janc
|
|
response 44 of 64:
|
Apr 16 13:45 UTC 1996 |
See? See? Just putting a program here on Grex means you have to work on it.
Apparantly the -s flag doesn't work. I got too many other things to do for
a while. I hope someone will fix this. If a non-staffer fixes it, I will
check it out and install the fixed version. Source is in /u/janc/src/watch.c
|
ajax
|
|
response 45 of 64:
|
Apr 16 18:55 UTC 1996 |
In line 131, s/>/>=/ . Was expecting 2 or more arguments when -s was used.
|
ajax
|
|
response 46 of 64:
|
Apr 16 23:44 UTC 1996 |
Whoops, forget that...the following is right, really! Replace 132 with....
for (first = 1; (first < argc) && (argv[first][0] == '-'); first++)
|
mdw
|
|
response 47 of 64:
|
Apr 17 09:41 UTC 1996 |
I just niced & killed several incarnations of a particularly hideous
watch script. We got to get one here. (sigh)
|
popcorn
|
|
response 48 of 64:
|
Apr 17 12:58 UTC 1996 |
[to clarify: the thing Marcus killed wasn't Jan's watch program, but rather
it was something someone else was writing]
|
robh
|
|
response 49 of 64:
|
Apr 17 15:48 UTC 1996 |
<robh breathes a sigh of relief>
|