shc@fred.UUCP (Steve Couturie) (02/28/91)
OK: To make ELM 2.3 Patch 11 work on Iris 4D: Do the Configure. Edit config.sh: d_vfork='undef' vfork causes ELM to fail to make locks d_flock='define' Sets locking style: This works for me. d_flockonly='undef' ditto libc='/usr/lib/libc_s.a' Use shareable library optimize='-O' Optimize it (why not!) ccflags='-D_BSD_SIGNALS' Use BSD style signals -- found "sigvec" in source libs='-lsun -lc_s' "-lsun" makes it work with YP. Then: sh ./config.h.SH sh ./Makefile.SH ( cd doc; sh Makefile.SH ) ( cd filter; sh Makefile.SH) ( cd hdrs; sh sysdefs.SH) ( cd src; sh Makefile.SH) ( cd utils; sh Makefile.SH) I also, however, get the error from "filter" when it tries to lock the system mailbox file. Filter commands like "savecopy" do this; I have no trouble with filter commands like "save <pathname>" though [I archive info-iris this way.] In order to keep incoming mail in the system mailbox, my .forward has both the "| filter ..." line and a line for sendmail to store everything in the default mailbox: "\shc". This works. (Filter does not use the same locking code as ELM itself does. This is not a feature :-) and I suppose should be fixed by the keepers of ELM.) Any other ideas out there? Steve -- Steve Couturie Voice: (213) 694-9332 Chevron Oil Field Research Co. FAX: (213) 694-7228 P.O. Box 446 Internet: shc@chevron.com La Habra, CA 90633-0446 UUCP: ...!uunet!lhdsy1!shc
hilchey@ucs.ubc.ca (Paul Hilchey) (03/01/91)
In article <9102272300.AA05961@fred>, shc@fred.UUCP (Steve Couturie) writes: |> |> OK: To make ELM 2.3 Patch 11 work on Iris 4D: |> |> Do the Configure. |> |> Edit config.sh: |> |> d_vfork='undef' vfork causes ELM to fail to make locks |> d_flock='define' Sets locking style: This works for me. |> d_flockonly='undef' ditto I ran in to some weird problems with elm that I traced back to flock, so I would recommend you use d_flock='undef' The problem showed up in a cluster of machines with shared mail spool and home directories. I never did track down exactly what was happening, but after running elm you could wind up not being able to read (using cat, for example) all of your mailbox. From some machines you could only read the portion of the file that existed prior to running elm. From the machine where you ran elm, though, you could read all of the file, and ls reported the correct file size from all machines. Elm does a stat on the mailbox and is unhappy if it can't read as many bytes as are supposed to be there. This was with Irix 3.3.1. ______ Paul Hilchey University Computing Services The University of British Columbia