not_ results from the CPAN

not_

AFS-Command

view release on metacpan or search on metacpan

    <HTML> 
	<HEAD> 
	    <TITLE>distro/Changes</TITLE> 
	</HEAD>

	<BODY>

<!-- INDEX BEGIN -->

<UL>

	<LI><A HREF="#CHanges_in_1_9">CHanges in 1.9</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<LI><A HREF="#Changes_in_1_8">Changes in 1.8</A>
	<LI><A HREF="#Bug_Fixes">Bug Fixes</A>
	<UL>

		<LI><A HREF="#vos_examine_did_not_pick_up_the_">vos examine did not pick up the LOCKED flag</A>
		<LI><A HREF="#pts_membership_error_checking_wa">pts membership error checking was bogus</A>
	</UL>

	<LI><A HREF="#Changes_in_1_7">Changes in 1.7</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<UL>

		<LI><A HREF="#Boolean_flags_can_be_turned_off_">Boolean flags can be turned off, as well as on</A>
	</UL>

	<LI><A HREF="#Bugs">Bugs</A>
	<UL>

		<LI><A HREF="#vos_examine_by_numeric_ID_did_no">vos examine by numeric ID did not parse Volume Headers</A>
	</UL>

	<LI><A HREF="#Changes_in_1_6">Changes in 1.6</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<LI><A HREF="#AFS_Object_VolumeHeader_new_a">AFS::Object::VolumeHeader: new attribute 'attached'</A>
	<LI><A HREF="#Bugs">Bugs</A>
	<LI><A HREF="#Changes_in_1_5">Changes in 1.5</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<UL>

		<LI><A HREF="#Principal_names_as_user_supplie">Principal names, as user supplied arguments, are lowercased</A>
		<LI><A HREF="#AFS_Command_VOS_restore_argum">AFS::Command::VOS->restore arguments added</A>
	</UL>

	<LI><A HREF="#Bugs">Bugs</A>
	<UL>

		<LI><A HREF="#AFS_Object_VolumeHeader_acces">AFS::Object::VolumeHeader 'accesses' attribute was incorrect</A>
	</UL>

	<LI><A HREF="#Changes_in_1_4">Changes in 1.4</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<UL>

		<LI><A HREF="#Test_suite_is_disabled_by_defaul">Test suite is disabled by default.</A>
	</UL>

	<LI><A HREF="#Bugs">Bugs</A>
	<UL>

		<LI><A HREF="#Volume_status_value_inconsistenc">Volume status value inconsistency</A>
		<LI><A HREF="#AFS_Command_VOS_examine_parse">AFS::Command::VOS->examine parses busy and offline messages</A>
	</UL>

	<LI><A HREF="#Changes_in_1_3">Changes in 1.3</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<UL>

		<LI><A HREF="#AFS_Command_VOS_release_suppo">AFS::Command::VOS->release support both -f and -force</A>
	</UL>

	<LI><A HREF="#Bugs">Bugs</A>
	<UL>

		<LI><A HREF="#AFS_Command_BOS_listhosts">AFS::Command::BOS->listhosts</A>
	</UL>

Changes.html view on Meta::CPAN


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

</A></H1>
A new argument is supported by AFS::Command::Base-&gt;new():


<P>

<PRE>    my $vos = AFS::Command::VOS-&gt;new( timestamps =&gt; 1 );
</PRE>

<P>

This will result in ISO timestamps being prepended to each line of output
when it is collected into the $vos-&gt;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
      (

( run in 0.769 second using v1.01-cache-2.11-cpan-39bf76dae61 )