release all locks on last close, not just those for this process
(not correct but better; needed for posix)
only sleep for remaining time in afs_osi_Wait if woken before timeout
add proto for afs_open
this probably needs a better fix. however, one some platforms, we see:
./snprintf.c: In function `afs_vsnprintf':
./snprintf.c:227: `short int' is promoted to `int' when passed through `...'
./snprintf.c:227: (so you should pass `int' not `short int' to `va_arg')
and it won't compile. are there platforms where short is correct?
freebsd 5.0 module now loads and runs!
init creds in osi_Init
don't call crhold on afs_osi_cred, because the mutex is invalid
afs_xioctl takes a thread, not a proc
FIXES 1614
This will allow access to AFS from system processes and scheduled tasks.
It also means that each user does not have to map AFS to his own
drive.
because the XDR struct is different on amd64, we need to do this to avoid tainting
namespace of processes which otherwise use XDR and wouldn't use ours otherwise.
this should be done otherwise, or maybe we *should* use the vendor XDR when we can.
add strlcat, strlcpy to libutil
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
src/util/strlcat.c src/util/strlcpy.c
To refresh your memories, this past semester, NC State experienced a
problem wherein the OpenAFS Client for Windows would go into a zombie state
and stop responding to traffic on the SMB interface until restarted...
break out i386 code from lwp/process.s to separate source file,
as discussed at workshop.
add support for OpenBSD 3.4, contributed by Brent Graveland <brent@graveland.net>
(requires kernel patch for lkm; see:
http://graveland.net/openbsd/openafs-on-openbsd
FIXES 1488
It adds:
- the binary version of the file version/productversion, which the MSI
engine sort of want files in MSI packages to all have. This requires
another variable to be maintained in NTMakefile.i386_nt40 (Please don't
change the value from 1,2,910,0 to 1,2,9,1 or something like that. The last
number group in the version is considered completely insignificant by some
things)
- some file typing, which I don't know if anything cares about
- Some new items in the stringfileinfo table, (InternalName and
OriginalFilename) without which explorer won't show use the version info in
constructing tooltip text.
- Actually setting ProductVersion and FileVersion to something real
- Language codes, which the MSI engine also wants
