Very Computer

1. More mail file locking questions (lockf, NFS, /var/spool/mail/*.lock)

        Here's a problem I've run into:

        The problem I've seen relates to building mh-6.8 for SVR4
        (and correspondingly LOCKF). Now, it appears that while
        INC believes the mail file (NFS mounted) should be
        locked, it isn't (or it is lockf'ed and someone else
        [/bin/mail?] isn't honoring the lock; it says something
        like "New mail has arrived.."). It appears that /bin/mail
        (on 4.1.x and Solaris 2.x) uses lock files
        (/var/spool/mail/*.lock).  

        My question is, should mh ({l}emacs, popper,imap,...)
        use this style (and abandon lockf), or is there some
        other appropriate solution to this problem?

        Thanks,

        Dave    

        David M. Meyer                  Voice:     503/346-1747
        Senior Network Engineer         Pager:     503/342-9458
        Office of University Computing  FAX:       503/346-4397

        University of Oregon
        1225 Kincaid
        Eugene, OR 97403        

2. Mosaic for svgalib

3. File locking text file in linux using C

4. ANSI Terminals, etc.

5. Solaris 2.5 system file table and file lock info for alerting on thresholds

6. Help with installing LINUX

7. File Locking on NFS files

8. Ethernet Initialization

9. File locking and data written to the end of a file

10. File locking and file permissions

11. File Locking with FILE pointers

12. File I/O improvements using file locking and/or mem-mapping???

13. partial file locking with ndbm(3) files