|
Grex > Agora > #4: Grex System Problems - Fall 2015/Winter 2016 | |
|
| Author |
Message |
| 25 new of 223 responses total. |
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!
|
cross
|
|
response 92 of 223:
|
May 18 14:53 UTC 2017 |
Happy to do it.
|
papa
|
|
response 93 of 223:
|
May 18 23:01 UTC 2017 |
My bbs already-read data was lost during the upgrade. Is it just me?
Not a major problem since I can gradually re-catch-up.
|
papa
|
|
response 94 of 223:
|
May 18 23:26 UTC 2017 |
emacs executable is no longer in my path. Did it move, or does it need to be
reinstalled?
|
cross
|
|
response 95 of 223:
|
May 19 00:25 UTC 2017 |
Try now. The installation was messed up.
Due to the age and, er, vintage of the version of OpenBSD running on Grex
before the upgrade, some commands were installed by hand. This caused
conflicts with the package system; the result in this case was a missing
symlink.
|
papa
|
|
response 96 of 223:
|
May 19 09:28 UTC 2017 |
Emacs is Back and Beautiful! :)
|
kentn
|
|
response 97 of 223:
|
May 19 22:03 UTC 2017 |
There was a new version of emacs on the old version of Open BSD already.
This one is probably the same or maybe a little newer. So it's not
like we didn't have it before.
|
cross
|
|
response 98 of 223:
|
May 19 23:33 UTC 2017 |
No one said we didn't.
But because the previous Grex had such an old ports collection, we had
to build that one from source; this caused port name conflicts with the
new version from the ports collection. As a result, the
/usr/local/bin/emacs ssymbolic link wasn't properly installed by the
package manager.
|
papa
|
|
response 99 of 223:
|
May 20 00:43 UTC 2017 |
What cross said.
|