The bosserver now logs the exit status of processes under its control.
====================
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.
====================
Messages generated as the result of assertion failures now include
timestamps.
- Adds the -crypt option, which causes rx connections to be encrypted
- Adds the 'vos setfields' command, which allows volume info fields to
be set. Currently, this command allows a volume's quota to be set,
and allows its dayuse counter to be manually cleared. At present,
no other changes are supported by the volserver RPC interface.
- Adds the 'vos changeloc' command, which allows the VLDB's idea of the
location of an RW volume to be explicitly changed without actually
moving the volume. This can be used in cases where the VLDB has the
wrong idea of the location of a volume for some reason. It is
somewhat more predictable and easy to understand than the syncserv
and syncvldb commands.
- Adds the -offline option to 'vos restore'. This option causes the
restored volume to be left offline. This functionality was already
present in the code but previously had no user interface.
- Adds the -readonly option to 'vos restore'. This option causes the
restored volume to be an RO volume. It is not permitted to restore
an RO volume when the associated RW volume already exists. While
it is possible to restore an RW volume where an RO volume exists,
caution should be used to avoid doing this with VLDB entries created
by 'vos restore -readonly', since such entries have their ROVOL and
RWVOL ID's set to the same thing.
This patch adds a "-long" option to rxdebug, to print out more verbose
output, and makes rxdebug print out more information about the Rx peers
when ran with "-long".
This patch provides better MTU selection on Solaris, by
actually going through the list of interfaces and picking
the correct MTU, rather than assuming 1500.
It also fixes a small bug in the server preference code,
which wasn't checking for IPv6 interfaces, and if there
were any IPv6 interface, it would believe all servers
were on the local subnet.
This patch fixes two bugs:
(1) pass more than 4 parameters to AFSCALL syscalls on Linux,
allowing the ADVISEADDR op to pass the MTU array pointer.
(2) properly convert MTU's to network byte order, since that's
what the rest of the code expects them to be.
hopefully this will be the end
(at least for a while) of problems where every linux version requires a new
openafs release. the struct vnode is now dynamically generated by parsing the
linux/fs.h file and pulling out the struct inode, then rewriting osi_vfs.h
perhaps too careful. to fix potential crash in TDel and TAdd
====================
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 extra ) which snuck in
based on observations of effects related to
afs-lookup-check-evalmountpoint-return-20010221 and affirmed based on
mail from Todd_DeSantis@transarc.com
this should reduce but perhaps not eliminate the VLRU cycle: increase
-stat parameter problem on Linux as it's not yet clear that this is the
only problem and circumstantially it is probably not.
this cuts rpc traffic in half for directories on which you have
no permissions and is capable of doing more if a useful way can
be conceived of caching errors.
currently bulkstat works thus:
say a directory has 100 files. bulkstat will on the first hit stat
the first 30 files, integrating the information if successful,
and when you hit file 31, repeat. meaning if you can read that 100 files
is 4 bulkstatus rpcs (3*30+10). if you can't, you do bulkstatus, get an abort,
then do fetchstatus on the file and find out why you lost. you go on and
try bulkstatus again this time for files 2-31 instead of 1-30. same failure,
meaning you do 2N rpcs for the N files. inlinebulk doesn't abort but instead
fills in stat info for any of the up to 30 files it can, and errors for
any it can't.
currently the client will pull out any stat info filled in,
and then return the error from the first file, meaning if you can't
read the directory we do N inlinebulk rpcs instead of N bulkstatus +
N fetchstatus rpcs. if the errors for the other 29 could be meaningfully
cached (and you have to be careful not to pollute information
such that it's not useful for someone in a different auth context) then
we could get down to the same 4 rpcs we have for success, but that's an
exercise for later give how the cache manager works.
====================
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.
====================
create audit event for inlinebulk
====================
rename spare2
there were some cases where we falsely reported the BZNOENT from salvage-tmp
being cleanup up as "bos: failed to start 'salvager' (no such entity)"..
despite having just reported:
bos: salvage completed
this should no longer happen.
-- /vicepX/AFSIDat/README is created the first time the fileserver
is started, rather than the second time.
-- For the namei fileserver, /vicepa/Lock/vicepa is created as
the lockfile. Previously, on Solaris, the raw device was
was being used for LockPartition(), and that breaks when
there isn't a corresponding device.
-- The VolPartitions and XVolPartitions volserver calls now return
the list of attached (rather than mounted) partitions. This is
consistent with the NT fileserver and removes duplicate code.
The actual magic for allowing the fileserver to attach non-mounted
partitions is to create /vicepX/AlwaysAttach.
====================
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.
====================
carefully avoid non vicep directories and/or partitions as it may get upset at
automounters or running cachemanagers!
====================
more carefully avoid non-vicepX partitions
