Anybody using nmh on 9.X?

[User Bp]

Hi all,

Has anybody gotten nmh working under 9.X?

Commands seem to hang. Sometimes hitting
control-C unsticks things and allows progress,
with a delay in reaction.

Mutt and mail both seem to behave normally, so
the trouble seems specific to nmh.

Thanks for reading!

bob prohaska

[Ted Nolan <tednolan>]

This is total speculation (I use it on 4.9 from time to time where
it works fine), but my first guess would be a mail spool locking
issue. Has maildrop locking changed on 9.X?

Looking at my 4.9 system, I see that in the Makefile for the nmh port,
you can choose:

NMH_LOCKING - specify the style of locking to be used by nmh for the
# users' spool files (e.g. the 'inc' command). Must match the
# locking style used by your MTA - the default is FLOCK_LOCKING
# (the documented behavior for the 'mail.local' delivery program).
# Do a 'make patch', then look in the source directory (currently
# the config.h.in file) for more information on different locking
# settings. Current valid settings are:
# DOT_LOCKING FCNTL_LOCKING LOCKF_LOCKING FLOCK_LOCKING

If that's still the case, you might try a different method there or in
config.h.
--
------
columbiaclosings.com
What's not in Columbia anymore..

[User Bp]

Ted Nolan <tednolan> <t...@loft.tnolan.com> wrote:
>
> Looking at my 4.9 system, I see that in the Makefile for the nmh port,
> you can choose:
>
> NMH_LOCKING - specify the style of locking to be used by nmh for the
> # users' spool files (e.g. the 'inc' command). Must match the
> # locking style used by your MTA - the default is FLOCK_LOCKING
> # (the documented behavior for the 'mail.local' delivery program).
> # Do a 'make patch', then look in the source directory (currently
> # the config.h.in file) for more information on different locking
> # settings. Current valid settings are:
> # DOT_LOCKING FCNTL_LOCKING LOCKF_LOCKING FLOCK_LOCKING
>
> If that's still the case, you might try a different method there or in
> config.h.

The Makefile no longer contains those lines, but it does contain:
CFLAGS = -O2 -pipe -DFLOCK_LOCKING -O -fno-strict-aliasing
which to my untrained eye suggests the same thing.

Letting the stalled command time out results in a complaint about
DISPLAY not being set; it's possible the binary expects an X
environment, though that was not my intent. Next step is to
remove the port entirely and try again.

Thanks for your help and encouragement!

bob

[Ted Nolan <tednolan>]

AH! That's very interesting. Is the stalled command "show"?

I think then what is happening is that your MHNPROC is getting invoked
for MIME messages, and it tries to open an xterm.

Assuming you use /bin/sh, bash or ksh, try this:

export NOMHNPROC=true

and then try your show command.

I suspect you'll see your message quickly this time, but that it will
not be de-mimed. If that's the case, you will want to look into different
mhnprocs that don't spawn an xterm.

Frankly, I just run with NOMHNPROC=true, and if a message shows up in
base64 or such intensive html that I can't read it on the screen, I then
do

mhn -store -auto

to de-mime and store as separate files and use less to read the
de-mimed text or lynx to read the html.