Excerpts from mail: 15-May-96 Re: AMDS problem with AFS3.4a Rudolph Todd
Maceyko@pit (1072+0)
> File locking has been a problem for us with shared AMS bboards using
> Solaris 2.4 clients running AFS 3.4a and AUIS 6.3.4. There was a file
> locking patch on the info-andrew list for makeboth.c (the White Pages
> update utility), but there needs to be another patch for the rest of
> AUIS to deal properly with the "new" return and errno values in Solaris
> 2.x.
It should be possible to make all of ATK's locking work correctly by
updating the definitions of:
#define osi_ExclusiveLockNoBlock(fid) hp_lockf(fid)
#define osi_UnLock(fid) hp_unlockf(fid)
#define osi_O_READLOCK O_RDWR
#define osi_F_READLOCK "r+"
in the system.h file for the platform in question.
The above was taken from the HP, where hp_lockf and hp_unlockf are
implemented in terms of fcntl. The same approach is probably what is
needed on Solaris.
Is there any standard rule to decide which locking system ATK should try
to use to maintain compatibility with AFS? For example, on AIX 3 it
seems that only lockf resulted in real locking on AFS.
-Rob Ryan
Andrew Consortium
