|
Grex > Agora > #4: Grex System Problems - Fall 2015/Winter 2016 | |
|
| Author |
Message |
| 25 new of 223 responses total. |
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.
|
papa
|
|
response 100 of 223:
|
May 20 00:57 UTC 2017 |
As I mentioned before, my backtalk/bbs viewing history got zapped during the
OS upgrade. Trying to re-catch-up on old posts has uncovered a new problem:
viewing history is not being updated (or not updated correctly) for
conferences other than Agora.
After reading new items and responses on Agora, I can use the NEXT command
to cycle through conferences in my list, but if I read the new items in a
conference (which, since viewing history was lost, is all items posted since
the beginning) then quit and restart bbs and again cycle through my conference
list with NEXT, the same conferences come up again showing new items, but
their the same items as I previously read.
Does that make any sense?
|
tod
|
|
response 101 of 223:
|
May 20 01:08 UTC 2017 |
Nice pager fix, Dan!
|
cross
|
|
response 102 of 223:
|
May 20 01:24 UTC 2017 |
resp:100 Not exactly, but try the "fixseen" command.
|
jhesse
|
|
response 103 of 223:
|
Jun 1 14:27 UTC 2017 |
So, since yesterday I'm not getting any new mail, with these errors in my
procmail logfile:
procmail: Lock failure on "/var/mail/jhesse.lock"
procmail: Error while writing to "/var/mail/jhesse"
From jhesse@fastmail.net Thu Jun 1 14:14:27 2017
Subject: testfoo
Folder: **Bounced**
My mail client sees nothing over imap. (No old or new mail) elm works as
normal, though.
Do I need to change something?
|
papa
|
|
response 104 of 223:
|
Jun 1 23:26 UTC 2017 |
Maybe related to jhesse's problem, yesterday I checked my Grex mail box for
the first time since the upgrade and was greeted with the message "Can't open
folder /var/mail/papa: no such folder" instead of the usual "0 messages in
inbox".
|
cross
|
|
response 105 of 223:
|
Jun 2 00:36 UTC 2017 |
Mail is now delivered into your home directory; so your mail spool file
is in ~/Mailbox. If you're sourcing the global dot files, you should get an
environmnet variable that tells mail programs and the like where to find
your mail.
|
cross
|
|
response 106 of 223:
|
Jun 2 00:36 UTC 2017 |
resp:103 Oh sorry; missed this earlier today. As as resp:105. If you're
setting $MAIL, then unset it; modify your .procmailrc accordingly.
|
jhesse
|
|
response 107 of 223:
|
Jun 2 15:08 UTC 2017 |
Thanks! .procmailrc is fixed, so I can get mail again through elm. IMAP and
POP still not working, though. My mail client says it can connect to both
and I'm not seeing anything contrary in the logs.
The server daemon is dovecot, correct? I don't know enough to know the
configuration.
|
kentn
|
|
response 108 of 223:
|
Jun 2 17:14 UTC 2017 |
Yes, IMAP is a problem now. It doesn't seem to know to look in our home
directory for the Mailbox file. I suspect this requires a bit of tweaking
of the dovecot config, but it is do-able.
|
cross
|
|
response 109 of 223:
|
Jun 2 20:59 UTC 2017 |
Funny... I updated the dovecot config the
other day. It should work. I'm out of town at
the moment, but will try and see about it if I
can login.
|