"EXT-Li, Yung A" <[EMAIL PROTECTED]> writes:
> > "EXT-Li, Yung A" <[EMAIL PROTECTED]> writes:
> > > I'm trying to use nmh-1.0.2 on HPUX 10.20 and I'm having this problem ...
> > >
> > > "Now, 'inc' won't work. The error says "can't fopen and lock
> > > /var/mail/<mymaildrop>"
[...]
> > On HP-UX 10.20, /var/mail is writable by the mail group, but not by
> > 'other'. Therefore, inc needs to be installed setgid mail. I just
> > installed nmh-1.0.2 on an HP-UX 10.20 machine and verified that this works
> > properly. Are you installing as root? If not, you won't be able to make
> > inc setgid.
>
> Unfortunately, I'm not root and can't get root on this box.
I know almost nothing about file locking, so I'll have to leave it to other
list members to comment on what one can do in such a situation. Perhaps nmh
should steal some of procmail's code -- it seems to be pretty robust in
terms of figuring out how it can do file locking successfully on all file
system types it's going to need to deal with.
By any chance did your /var/mail used to be a local filesystem but now your
system administraors have changed it to be NFS-mounted? Perhaps that's why
the file locking is failing.
> > Or did you perhaps re-run configure? nmh-1.0.2 had a bug (now fixed in the
> > latest nmh-1.0.2+dev source) where if you re-ran configure the name of the
> > group owning the mail spool would become NULL in uip/Makefile.
>
> I did re-run configure.
Well, that was my point, you don't _want_ to, since re-running breaks
uip/Makefile.
> But I've even wipe out the source tree and re-extracted the tar
> files. Same problem.
Which same problem? It still wants to run autoheader? That shouldn't be
the case -- the timestamps are set up correctly. You can use make -d to
find out why it's trying to do that (perhaps your make is broken). With
judicious use of 'touch', you can prevent unnecessary make actions.
Or did you mean the other problem, the /var/mail locking one? If so, my
previous comments apply.
> Also, the doc. seems to suggest that I can change "mts.conf" to change the
> locking behavior. But it seems like I have to change "config.h" and
> recompile.
>
> Is this right?
Oh, yes, you're right. The documentation on file locking shouldn't really
be in the mh-tailor man page, since it's a compile-time option, not
configurable by mts.conf. Maybe someone moved the documentation there
anticpating making it run-time configurable or something...
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
