it seems like this might be a bug in solaris10 when handling contracts
of exiting chilren who have created kernel threads. the rxlistener is
a kernel thread on solaris and the child that starts the kernel_thread
returns and exits.
====================
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.
====================
incorporating STABLE14-macos104-20051005 STABLE14-macos-cleanup-20051006 macos-cleanup-20051006 macos-cleanup-20051007 from the 1.4.x branch, which needed to be forward-ported to work here, sadly.
There was a race condition associated with maintaining the
CM_FILELOCK_FLAG_CLIENTONLY flag on locks bound to scache entries
for Read Only volumes. Therefore, we remove the use of the flag
and simply test the RO status of the scache entry.
anyway, implement dentry cache status dumping for linux.\7f and provide a tool to dump it
disabled (tool, not rpc) by default
====================
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.
====================
perhaps this should never be pulled up.
anyway, implement dentry cache status dumping for linux.^? and provide a tool to
dump it
disabled (tool, not rpc) by default
====================
perhaps this should never be pulled up.
anyway, implement dentry cache status dumping for linux.^? and provide a tool to
dump it
Discovered a failure in the state machine. There was no method of
distinguishing between all servers being Down (which is handled by the
background thread) and all volumes being offline (perhaps due to a move).
Do not mark locks lost simply because the ExtendLock failed.
A lock is only lost if the server responds with EINVAL indicating
that the lock no longer exists. A lock can be renewed by other clients
that are also using the file. The client can make no assumptions about
the status of a lock based upon the passage of time.
As the file name of the OpenAFS installer changes with each release,
so must the Product ID (but not the Upgrade ID). Therefore, do not
hard code the Product ID in the Makefile, instead auto-generate it
as part of the installer.
The shell extension is unloading as it should but is never being loaded
again. Since we have no clue why and no idea how to debug it, for now,
just prevent it from being unloaded in the first place.
Add reporting of the FID, cell, owner and group to the output of "fs exa"
(on Windows only). There is no other means to obtain this data from a
Windows client.
For the afscreds program on Windows, if you right click the system tray icon
to display the menu and then click on the taskbar, the menu is not hidden,
but instead is covered by the taskbar.
This is a common issue documented at
http://support.microsoft.com/default.aspx?scid=kb;en-us;135788.
Install a Documentation Shortcut as part of the client install.
It is independent of the Supplemental Documentation which is not
required for the release notes.
Update the installer to always install the release notes.
====================
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.
====================
Update the installed documentation to include the new OpenAFS for
Windows release notes. No IBM documentation is being removed but
the top level index page has been re-written to indicate that the IBM
docs are out of date. The new OAFW Release Notes have been added to
the ReleaseNotes with a link.
====================
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.
====================
remove the logic in cm_Analyze that performs a flush of the server
data and retries when all of the servers are marked down (aka ALLOFFLINE).
Instead return an immediate error to the caller. The servers will be
checked by the background daemon thread and made available when they are.
* add a version of rxi_DebugPrint for Windows that uses OutputDebugString
* migrate all printf statements to the dpf macro
* stop masking the errors from rx_sendmsg() so that higher level functions
can make decisions based upon the failure.
* Windows reports EHOSTUNREACHABLE. Similar to Linux, if it is reported
reset the send packet start time to 0 in order to immediately cause the
server to be marked down.
heavily reworked by jaltman@secure-endpoints.com
and then a little further editing by me
see if we can avoid doing to sleep forever waiting on the tq to flush
====================
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.
====================
do not decrement tqWaiters in the while evaluation. This will
result in an invalid count if the value was zero to begin with.
Begin to store the Disk Volume Serial Number and Machine SID in the
AFSCache file for use in detecting system clones. Clones must get
a new UUID for the AFS Client.
"fs flushall" is like "fs flushvolume" but flushes all data in the cache
====================
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.
====================
When updating cell information from DNS, be sure to set a new timeout.
When obtaining cell information from a file, check every two hours to
see if it changed.
Add support to allow use of \\AFS\<foo> where <foo> is either a mount
point or symlink. As <foo> is normally treated as a share name, we
transform it into \\AFS\all\<foo> for processing.
projects / packages / o / openafs.git / log