view release on metacpan or  search on metacpan

Changes.html  view on Meta::CPAN

when it is collected into the $vos->errors(). This is useful for
profiling the performance of operations such as vos release:


<P>

<PRE>    my $result = $vos-&gt;release
      (
       id               =&gt; 'somevol',
       cell             =&gt; 'somecell',
      ) || die $vos-&gt;errors();
</PRE>

<P>

When this works, the $vos-&gt;errors() will have the verbose output, which
can be logged even in the successful case, for diagnostics. Here's an
example for a failure:


<P>

<PRE>    [2004-11-18 17:20:36] Could not lock the VLDB entry for the volume 536998569.
    [2004-11-18 17:20:36] VLDB: no permission access for call
    [2004-11-18 17:20:36] Error in vos release command.
    [2004-11-18 17:20:36] VLDB: no permission access for call
</PRE>

<P>

<P>
<HR>
<H1><A NAME="Changes_in_1_8">Changes in 1.8

</A></H1>
<P>
<HR>
<H1><A NAME="Bug_Fixes">Bug Fixes

</A></H1>
<P>
<HR>
<H2><A NAME="vos_examine_did_not_pick_up_the_">vos examine did not pick up the LOCKED flag

</A></H2>
The code to parse the VLDB header was missing the LOCKED flag, if it was
present, so this attribute was not being set properly. It is now.


<P>

<P>
<HR>
<H2><A NAME="pts_membership_error_checking_wa">pts membership error checking was bogus

</A></H2>
Well, it still is bogus, actually, since the code has to deal with the fact
that pts has never produced meaningful return codes, so a failed pts
membership command can still exit 0, and we have to figure out if it failed
by other means. This is done by looking for the known error messages that
pts prints out, which is a good example of why parsing the ASCII test
output of commands like this is a weak architecture.


<P>

<P>
<HR>
<H1><A NAME="Changes_in_1_7">Changes in 1.7

</A></H1>
<P>
<HR>
<H1><A NAME="Enhancements">Enhancements

</A></H1>
<P>
<HR>
<H2><A NAME="Boolean_flags_can_be_turned_off_">Boolean flags can be turned off, as well as on

</A></H2>
If an argument to a method (and its corresponding command line argument)
doesn't take a value, it is treated like a Boolean flag. However, the code
used to assume that the existence of a Boolean key in the argument list
implied the Boolean argument was always true.


<P>

Now, the truth of the arguments <EM>value</EM> is tested to determine if the flag should be set on or off. This makes it
easy to have subroutines that just blindly pass certain arguments along,
without haing to test them, and allows for much cleaner code.


<P>

For example:


<P>

<PRE>    my $result = $vos-&gt;release
      (
       name             =&gt; $name,
       force            =&gt; $force,
      );
</PRE>

<P>

Will work as you probably expected it to, namely if <CODE>$force</CODE> is
zero, it will NOT be passed to the ``vos release'' command. In previous
releases, regardless of the value of $force, the mere existence of the
force key in the argument hash would have caused the -force option to be
used.


<P>

<P>
<HR>
<H1><A NAME="Bugs">Bugs

</A></H1>
<P>
<HR>
<H2><A NAME="vos_examine_by_numeric_ID_did_no">vos examine by numeric ID did not parse Volume Headers

</A></H2>
The code to parse the volume headers in the output from ``vos examine'' was
looking for a pattern match based on the ``id'' argument. However, the
headers always print the name first, and we were assuming that the id
argument was the volume name, when it can also be the volume ID.


<P>

The parsing is less strict now, and works for both a volume name od a
numeric ID.


<P>

<P>
<HR>
<H1><A NAME="Changes_in_1_6">Changes in 1.6

</A></H1>
<P>
<HR>
<H1><A NAME="Enhancements">Enhancements

Changes.html  view on Meta::CPAN

<P>

For example, you can pass a mixed case string to pts-&gt;creategroup(), and
then use the same string to query the resulting AFS::Object::Group object
using <CODE>getGroupByName().</CODE>


<P>

The object's ``group'' attribute, however, will be in lower case, since
that will be the value returned by the pts command itself.


<P>

<P>
<HR>
<H2><A NAME="AFS_Command_VOS_restore_argum">AFS::Command::VOS->restore arguments added

</A></H2>
Documentation for two important new vos restore arguments was added to the
documentation (-creation and -lastupdate). These options are only available
in a patch to vos, which should be in one the next two major OpenAFS 1.2.X
releases.


<P>

<P>
<HR>
<H1><A NAME="Bugs">Bugs

</A></H1>
<P>
<HR>
<H2><A NAME="AFS_Object_VolumeHeader_acces">AFS::Object::VolumeHeader 'accesses' attribute was incorrect

</A></H2>
The actual attribute on the objects was named ``access''. Oops. The
attribute was changed to ``accesses'' to match the documentation, and the
string that is parsed in vos output.


<P>

<P>
<HR>
<H1><A NAME="Changes_in_1_4">Changes in 1.4

</A></H1>
<P>
<HR>
<H1><A NAME="Enhancements">Enhancements

</A></H1>
<P>
<HR>
<H2><A NAME="Test_suite_is_disabled_by_defaul">Test suite is disabled by default.

</A></H2>
There is a well intentioned effort to automatically test all new
submissions to CPAN (see <A
HREF="http://testers.cpan.org).">http://testers.cpan.org).</A>
Unfortunately, the AFS-Command package can't be tested automatically, since
it requires a fair amount of configuration. You have to specify a cell
name, some fileserver names and partitions, etc.


<P>

By default, the tests will all be skipped if the configured cell name in
the CONFIG file has not been modified, thus allowing the automated CPAN
testing to continue, automatically, without the author getting a bunch of
bogus emails.


<P>

<P>
<HR>
<H1><A NAME="Bugs">Bugs

</A></H1>
<P>
<HR>
<H2><A NAME="Volume_status_value_inconsistenc">Volume status value inconsistency

</A></H2>
!!!!!!!! WARNING !!!!!!!!


<P>

This change is NOT backwards compatible with previous releases, so verify
that your code handles the new, consistent values correctly.


<P>

The ``status'' field returned from either vos-&gt;examine() or
vos-&gt;listvol(), in previous releases, had inconsistent values. When a
volume is online, the status would be one of:


<P>

<PRE>    online
    On-line
</PRE>

<P>

Likewise, when offline, one of:


<P>

<PRE>    offline
    Off-line
</PRE>

<P>

These values have all been normalized to: online, offline


<P>

<P>
<HR>
<H2><A NAME="AFS_Command_VOS_examine_parse">AFS::Command::VOS->examine parses busy and offline messages

</A></H2>