head 1.4;
access;
symbols
RPM_4_2_1:1.1.1.1
RPM_4_2:1.1.1.1
RPM_4_1_1:1.1.1.1
RPM_4_0_5:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.4
date 2008.01.02.09.55.32; author rse; state dead;
branches;
next 1.3;
commitid z4cpSiAhOCXk5PLs;
1.3
date 2003.08.24.12.43.16; author rse; state Exp;
branches;
next 1.2;
1.2
date 2003.08.24.12.33.51; author rse; state dead;
branches;
next 1.1;
1.1
date 2002.08.14.16.32.05; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2002.08.14.16.32.05; author rse; state Exp;
branches;
next ;
desc
@@
1.4
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: RPC FAQ
- Berkeley DB Reference Guide:
- RPC Client/Server
|
  
|
RPC FAQ
- I get the DB_NOSERVER error back from a
DB_ENV->set_rpc_server call that is using the default client
timeout value.
Some systems have a default RPC client timeout value that is too small,
and the client times out the request before the server has a chance to
process and reply. If you get this error, try explicitly setting the
client timeout value.
Copyright Sleepycat Software
@
1.3
log
@Resolve: RPM 4.1 -> RPM 4.1.1
@
text
@@
1.2
log
@Resolve: RPM 4.0.5 -> RPM 4.1
@
text
@@
1.1
log
@Initial revision
@
text
@@
1.1.1.1
log
@Import: RPM 4.0.5
@
text
@@