|
Grex > Agora > #4: Grex System Problems - Fall 2015/Winter 2016 | |
|
| Author |
Message |
| 25 new of 223 responses total. |
kentn
|
|
response 67 of 223:
| 
Apr 10 23:36 UTC 2017 |
It takes some time to set things up, and of course, we need to
(according to some) start over with just a few of standard starter
items. So, we could see how it would work...Spring/Summer. We
don't really have a cfadmin any more, who would normally do this.
|
tod
|
|
response 68 of 223:
|
Apr 11 03:39 UTC 2017 |
re #62
Once upon a time I could rely on UM ITD but they removed me like Napoleon
Bonaparte
|
ryan
|
|
response 69 of 223:
|
Apr 28 14:13 UTC 2017 |
Just a FYI -
When logging in, the default tset command in my .profile was choking on what it
was finding my terminal to be: "screen.xterm-256color".
Fixed it by export TERM="vt100" in my .profile.
|
tod
|
|
response 70 of 223:
|
Apr 28 23:46 UTC 2017 |
vt102 is better!
|
kentn
|
|
response 71 of 223:
|
May 13 22:36 UTC 2017 |
Looks like we upgraded to OpenBSD v6.1. I see the webserver is not
running so we can't use the RT help desk, nor is our imap daemon
(dovecot). bbs is operating somewhat differently (fixseen doesn't fix
things completely, and there were tons of new responses that were not
new. Also the scrolling is showing an entire screen for one response
i.e. lots of white space). Am assuming this is all in process now and
will be fixed as we go along. Knowing how much trouble our last upgrade
to OpenBSD caused, I hope we can get past this one in good shape without
a lot of hassle. Thanks so much for this effort to upgrade grex!
|
cross
|
|
response 72 of 223:
|
May 14 02:56 UTC 2017 |
For the weird blank lines thing, add the `-c` option to your pager
command line, if you are using `less`.
|
cross
|
|
response 73 of 223:
|
May 14 02:56 UTC 2017 |
Oh and PS: we are definitely hitting some bugs in backtalk.
|
kentn
|
|
response 74 of 223:
|
May 14 04:04 UTC 2017 |
Thanks!
|
kentn
|
|
response 75 of 223:
|
May 14 21:16 UTC 2017 |
Yes -c fixed the issue. In fronttalk you can change your pager
using the DEFINE command. DEFINE PAGER will show what you currently
have for a pager. HELP DEFINE will show how to use DEFINE.
|
papa
|
|
response 76 of 223:
|
May 14 23:53 UTC 2017 |
The party 5-minute-idle-boot is an annoying "feature" that the upgrade seems
to have awakened.
|
kentn
|
|
response 77 of 223:
|
May 15 02:28 UTC 2017 |
Will we install dovecot or something similar for IMAP e-mail access?
We had it running previously.
I'm still not sure how the help desk is going to work if we don't have
RT working on the new system. While there are ways around this, we need
to let people know, and those of us doing validations and other help
tasks need some way to see the requests come in and answer them.
|
cross
|
|
response 78 of 223:
|
May 15 12:19 UTC 2017 |
resp:76 What five minute idle timeout?
resp:77 Dovecot is installed and running.
|
cross
|
|
response 79 of 223:
|
May 15 12:22 UTC 2017 |
I think I found (and fixed) the idle timeout thing.
|
kentn
|
|
response 80 of 223:
|
May 15 21:42 UTC 2017 |
Thank you, Dan! Upgrades are a lot work, I know.
|
papa
|
|
response 81 of 223:
|
May 16 22:32 UTC 2017 |
Thanks for fixing 5-minute idle boot and first-character-swallowing problems
on party.
|
papa
|
|
response 82 of 223:
|
May 16 22:41 UTC 2017 |
In bbs, the pager (grexmore?) prompt "- (END)[Press space to continue, q to
quit, h for help]" is being displayed and output paused before a full page
of text has been printed. An extreme example is after entering r*ead at the
Ok: prompt, the pager pauses and displays its prompt immediately after the
command is entered before any text is displayed.
Is there an environment variable or something that needs to be set to fit our
actual terminal size?
|
cross
|
|
response 83 of 223:
|
May 17 01:04 UTC 2017 |
Look at the page size data in `stty -a`? Is it weird looking?
|
papa
|
|
response 84 of 223:
|
May 17 17:32 UTC 2017 |
42x80 looks OK
|
commodorejohn
|
|
response 85 of 223:
|
May 17 17:52 UTC 2017 |
stty -a reports 80x24, which is what my PuTTY session is set to. But I see
this behavior as well - sometimes it'll print a single line of text in bbs
and then fire off a pager prompt.
|
cross
|
|
response 86 of 223:
|
May 17 19:14 UTC 2017 |
That's weird....
To be honest, I'm actually having a hard time even visualizing quite what you
guys mean. Can someone post a screen shot somewhere or something?
|
tod
|
|
response 87 of 223:
|
May 17 21:29 UTC 2017 |
It's weird now...it shows how many bytes have been read until then the
last Page says (END)
|
tod
|
|
response 88 of 223:
|
May 17 21:30 UTC 2017 |
- (END)[Press space to continue, q to quit, h for help]
|
papa
|
|
response 89 of 223:
|
May 18 00:08 UTC 2017 |
Screen shot: http://grex.org/~papa/tmp/premature-pager.png
I entered "r" at the Ok: prompt to read the new messages. bbs should either
print the first new message completely if the message is 42 lines or less,
or print the first 42 lines and then the "...Press space to continue..."
prompt. Instead, it prints the pager prompt immediately after I enter "r"
without printing any message text.
|
cross
|
|
response 90 of 223:
|
May 18 01:00 UTC 2017 |
Thanks, now I think I understand what you mean.
I wonder if it's trying to print some kind of prefix file or something, and
that file happens to be zero length....
Please give it a go now. `more` was replaced with `less`, and when you invoke
`less` as `more`, it enters a compatability mode, but it's not exact.
|
papa
|
|
response 91 of 223:
|
May 18 10:57 UTC 2017 |
The pager problem appears to be solved. Thanks!
|