|
|
| Author |
Message |
| 25 new of 283 responses total. |
steve
|
|
response 75 of 283:
| 
Jan 15 16:16 UTC 1999 |
If you look at the file /etc/nologin.boilerplate you'll see what
will be placed in /etc/nologin if I type 'nologin' as woot. Feel
free to suggest different phrasing, etc. This really is a good
idea. Thanks Greg, for suggesting it.
|
keesan
|
|
response 76 of 283:
|
Jan 15 16:38 UTC 1999 |
Thanks Scott and STeve.
|
ryeguy
|
|
response 77 of 283:
|
Jan 15 17:35 UTC 1999 |
my sister is an idiot is my sister doth she be
blah
|
flem
|
|
response 78 of 283:
|
Jan 15 18:05 UTC 1999 |
re 75: the spelling gestapo might suggest that you substitute "explanation"
for "explaination", but other than that it looks good.
|
steve
|
|
response 79 of 283:
|
Jan 15 18:20 UTC 1999 |
Got it.
|
aruba
|
|
response 80 of 283:
|
Jan 15 18:20 UTC 1999 |
And the grammar KGB might object to "the staff are working", presuming they're
based in America and not England. But it looks good to me too.
|
remmers
|
|
response 81 of 283:
|
Jan 15 21:08 UTC 1999 |
And the ambiguity nannies might complain that the last sentence
could be interpreted to mean that getting Grex to work is not an
improvement.
|
steve
|
|
response 82 of 283:
|
Jan 15 22:02 UTC 1999 |
Ha! I guess thats right.
|
void
|
|
response 83 of 283:
|
Jan 15 23:01 UTC 1999 |
other than what has already been pointed out, it looks pretty good
to me, too. even so, i rather like "grex is being cranky right now.
call back in a little while," too.
|
hhsrat
|
|
response 84 of 283:
|
Jan 16 02:26 UTC 1999 |
Just for those of us who do not always telnet in, and even if they did
don't know how to read a file: Could you please post the contents of
/etc/nologin.boilerplate in this item?
|
steve
|
|
response 85 of 283:
|
Jan 16 02:50 UTC 1999 |
Sure...
Grex is not allowing people to log in right now, because of a
problem that the staff are working on. This is the generic
message that is placed when there isn't time for further
explaination of a problem. Please check back in 20 minutes
or so to see if the situation has improved or if Grex is once
again working.
|
keesan
|
|
response 86 of 283:
|
Jan 16 02:58 UTC 1999 |
Typo on 'explanation', message is very understandable.
|
hhsrat
|
|
response 87 of 283:
|
Jan 16 03:09 UTC 1999 |
thanks.
The last sentence seems like (to me anyways) it's saying
To see if the situation has improved OR grex is actually working.
That makes it seem like a working grex is not a good thing (at least to
me)
|
scg
|
|
response 88 of 283:
|
Jan 16 04:18 UTC 1999 |
"a problem that the staff are working on" sounds very English.
|
steve
|
|
response 89 of 283:
|
Jan 16 04:37 UTC 1999 |
Thanks. Spelling noted and corrected.
|
davel
|
|
response 90 of 283:
|
Jan 16 13:25 UTC 1999 |
Possibly "Please check back in 20 minutes or so. We may be up or have more
information then." ?
|
dpc
|
|
response 91 of 283:
|
Jan 17 16:53 UTC 1999 |
A nice fix, STeve!
|
mdw
|
|
response 92 of 283:
|
Jan 18 03:45 UTC 1999 |
I'd suggest "1 hour" instead of 20 minutes.
|
ydesai
|
|
response 93 of 283:
|
Jan 18 08:57 UTC 1999 |
Hi htere its yash I would like to joiin you too
|
davel
|
|
response 94 of 283:
|
Jan 18 13:05 UTC 1999 |
This is a system problem?
|
keesan
|
|
response 95 of 283:
|
Jan 18 16:16 UTC 1999 |
I emailed him and suggested he try party instead of bbs, or tell us more about
himself in item 1 of agora.
|
janc
|
|
response 96 of 283:
|
Jan 20 13:11 UTC 1999 |
I'll have to look at item forgetting in Backtalk.
Couple notes however:
- You cannot safely have Backtalk and Picospan in the same
conference at the same time. When you enter a conference with
Picspan, it reads the participation file into memory, and doesn't
write it out until it leaves the conference. Any changes made by
Backtalk in the interim will be overwritten by Picospan. You can
safely have multiple Backtalk windows on the same conference though.
- You can't do what Valerie said she was trying to do - that is have
an item forgotten with no responses read. The Picospan
participation file marks forgotten items by negating the number
of responses read. You can't negate zero. If you forget a new
item with Backtalk, it is supposed to mark one response (or rather,
the item text) read, before forgetting it. I seem to remember
Picospan gives an error message if you try to do this.
|
davel
|
|
response 97 of 283:
|
Jan 21 02:05 UTC 1999 |
Hmmm. I use Picospan, not backtalk. I have forgotten new, unread items, and
it appears to work fine. I just went to test & tried it, & it seemed to work.
Secondly, I *think* it's "set autosave" that causes Picospan to write out the
participation file after each item is read. (This is listed in the help for
"set" but there is no help for "set autosave", so I'm not entirely sure.)
I don't know whether Picospan ever rereads the participation file, though,
but I suspect not; so even with set autosave turned on having Backtalk &
Picospan (or 2 copies of Picospan) reading the same conference simultaneously
for the same user probably is asking for trouble.
("help summary" gives help (and some error messages, which I think I remember
posting as a system problem 5 or 6 years ago <sigh>), and it includes the
following line:
autosa_veseen -automatically save particpipation file while READing
So I think that is the command in question.)
|
jeff
|
|
response 98 of 283:
|
Jan 21 04:24 UTC 1999 |
my .cflist and .cfonce don't work anymore :(
|
jeff
|
|
response 99 of 283:
|
Jan 21 17:26 UTC 1999 |
oops..I forgot to mv my .cflist anf .cfonce to my .cfdir :P
|
