"In the original version the path name in the box showing the network
drives were wrong if a part of the name after afs had only 3 characters:
afs\ipp\u became afs\u. Also the small hooks in front of the names
disappeared immediately."
"Under 2.4.x kernels, there is a file type in the result of readdir to
help applications optimize directory traversal. With usfficiently new
libc compiled against sufficiently new kernel headers, this is exported to
applications.
Several applications, including fileutils use this information. AFS
asserts that all files are directories. This sucks, because among
other things it causes rm -rf not to work."
Makefile.am and configure.in first cuts. not yet useful
====================
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.
====================
oops; this belongs on the branch created for autoconf development
in the same way members of system:administrators have all pts powers,
members of system:ptsviewers have all pts read powers by virtue of
said membership
use uint64_t in preference to u_int64_t as solaris has only the latter and
linux appears to have both. also, use lockf where flock was used in the
solaris case
setup for darwin port
====================
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.
====================
changes for darwin port
====================
added files for the darwin port
====================
changes for darwin port
" rx: attempt to fix incorrect rtt computation, possibly winning
on performance for links with some packet loss.
Currently, the rtt is computed as the time from the transmission
of a packet until the receipt of the corresponding ack packet.
But this includes a potential delay (rx_{soft,hard,last}AckDelay)
on the client which results in an abnormally high rtt, and even
more erroneous rtt_dev and retransmit timeout values.
The proposed solution is to ignore RX_ACK_DELAY type ack packets
for the purposes of rtt computations, and introduce another ack
packet type for RX_ACK_DELAY-type acks which are sent immediately
by the client.
This should of course be backwards-compatible with existing clients.
"
Changes for Alpha to previous 64 bit changes for sparc (sparc64 isn't
necessarily analogous to alpha or any other 64 bit linux platform)
====================
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.
====================
use mkstemp
====================
Include necessary file for alpha config
====================
Deal with 64 bit time_t
====================
Don't do increments in a way that can be miscompiled
====================
configure for alpha linux
====================
deal with time and initialize a variable
====================
don't use ViceIoctl32 for alpha linux
====================
deal with compiling kdump for alpha linux
====================
mods in callback.c analogous to dux port; mods in viced to deal with
thread creation function return convention
====================
config for linux alpha
====================
ids for alpha linux consistent with new-style sysname grouping
====================
makefile and config files for new-style sysnames
====================
MakefileProto changes for alpha linux with new-style sysnames. A change
in config/mc.c will be needed for this to configure correctly, and it will
be added soon
====================
note alpha port and the state it's in to hopefully avoid questions
Add support for syslogging server log messages
====================
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.
====================
Add syslogging capability to ptserver
====================
add syslog capability to fileserver
====================
Add syslog capability to the volserver
====================
Add syslog capability to the vlserver
====================
fix my own error when hand-applying nathan's patch
====================
remove unused function
"First, some background: The AFS Fileserver tries really hard to keep
track of all the "interfaces" of a client. Generally this is for a
multi-homed client, so that the server realizes that you are the same
client when you come from multiple addresses. However, this also
winds up applying to a mobile host whose IP address changes over time.
When the Fileserver sees a "new" address, it asks the client for its
Uuid and, if that Uuid already exists, it adds this new address to the
list of interfaces for the existing host. However, it keeps a
callback connection open to the original address.
Here's the problem: Assume the client has callbacks registered with
the server and then disappears from the network. While the client is
off the net, someone else makes a change that causes that callback to
be broken. The fileserver can't reach the client, so the break gets
added to the delayed callback list. The logic is such that no client
requests will be processed by a host while there are outstanding
delayed callbacks to that client.
Now, if the client comes back on the same IP Address, everything works
fine. The fileserver uses the cached callback connection and the
callbacks are cleared successfully. However, if the client returns to
the network under a different address, this new address is added to
the existing host structure and then the delayed callbacks are
attempted. Unfortunately it is using the (invalid) cached connection
to the old IP Address, so the delayed break fails. Therefore, this
client is locked out of the fileserver until:
1) the fileserver reboots,
2) the client returns to the original IP Address, or
3) All the callbacks timeout on their own.
This patch will fix this problem. When the client makes a request and
the fileserver tries to break the delayed callbacks, if the breaking
fails then the fileserver will attempt to find a 'working' interface
by probing all the host interfaces for one that responds with the
correct Uuid. If that succeeds then it resets the cached callback
connection and then breaks the delayed callbacks, thereby regaining
the connection to the client and proceeding with the proper cleanup
before the original request is completed."
Avoid condition where we could read past the end of lrealm (unlikely
to occur in practice and not remotely exploitable; cell and lrealm are
both MAXKTCREALMLEN and lrealm is configured locally and not read from the
network)
"Here are the symptoms. I have 2 OpenAFS Linux 2.4 machines, one SMP and
one not.
--With both of them I access a series of directories and files within
(/afs/w/x/y/z/).
--I then move to the root directory.
--From a third machine, I remove the directories x, y, and z. Then re-add
them (same names) with some other files.
--From the SMP box, I do an ls in /afs/w and see x. But x is inaccessible.
--From the UP box I can see and access x.
"
====================
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.
====================
Missed earlier: not part of the IBM delta.
====================
Part of the alpha patch slipped into the delta; Revert to previous
revision
"Simple patch to add "-syslog" option to bosserver. Causes it to direct all
logging activity to syslogd instead of to logs/BosLog"
currently unimplemented for NT
====================
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.
====================
Don't use a static outside its scope
"This prevents pts from crashing like this:
pepsi-one~> pts createg a:b -id -1234
/bin/athena/pts: Permission denied ; unable to create group a:b with id -1234
owned by 'Segmentation fault
"
" I have found problem with file locking and 64bit linux (tested on
ultrasparc). When issued fcntl(fd, f_SETLK, ..) with l_start = 0 and l_len
= 0, it sets l_len to LONG_MAX, so it is needed to test this value"
