[OpenAFS-devel] Re: Multiple databases in ubik

Sun, 18 Dec 2011 10:09:54 -0500

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigEE4DAB0F9854CA5A02719AB3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
    <title></title>
  </head>
  <body bgcolor=3D"#ffffff" text=3D"#000000">
    On 12/18/2011 9:54 AM, Derrick Brashear wrote:
    <blockquote
cite=3D"mid:CAMHoRJj9ijRNymM3TZML-8d-eExz4Cff0KWovwiVuGDyM1XOtg@mail.gmai=
l.com"
      type=3D"cite"><br>
      <blockquote type=3D"cite">
        <pre wrap=3D"">RXGEN_OPCODE is an indication that the RPC is inte=
ntionally not
supported and can be used to indicate failover to an alternate RPC.

RXGEN_SS_UNMARSHAL is an indication that the server and client mismatch
and the client should stop communicating with the server to prevent data
corruption.
</pre>
      </blockquote>
      <pre wrap=3D"">
I'd still rather see dummy stubs that return that, then, explicitly,
rather than RPC number reuse.

</pre>
    </blockquote>
    <br>
    I'm in complete agreement.=C2=A0 I was explaining why RXGEN_SS_UNMARS=
HALL
    is not an acceptable return code to use for an RPC upgrade.<br>
    <br>
    Jeffrey Altman<br>
    <br>
  </body>
</html>


--------------enigEE4DAB0F9854CA5A02719AB3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJO7gJEAAoJENxm1CNJffh4FKIH/R03gf2oRW/IbCfhivaPAXcX
BG8wIdTcHyqOIEiRl7K1REoXHF4CCldQcALpIb17vhd7bdfXJgGchW14Gc5tuCWU
94GjnAksODpLTYpUuPUqAzya9dQeIE7q2bXzTdfuK6bXz+HEQdlA4WS1cboVguWb
5mWAOhRaxYZYvGU4Dg9ePlS7KFWCVvEaXRliwf5shSxD3U8TrvoJlmuhvM5qP9AX
w1ZmzsgzR/3upcdZxHjn51fsSc6f3V82FYMZpFiQZ2axW1ya4neFvgo7gx6fY1LS
7UFeLmQhB2y29CaOI74VLcwJFqTgN7JryHwW2NWOXiqvIsQPyu2yGvICvmiFzzM=
=K4vC
-----END PGP SIGNATURE-----

--------------enigEE4DAB0F9854CA5A02719AB3--