1DC_SNOOP(1) distcache DC_SNOOP(1)
2
3
4
6 dc_snoop - Distributed session cache traffic analysis
7
9 dc_snoop -listen <address> -server <address> [options]
10
12 dc_snoop runs as a transparent proxy supporting the distcache(8) proto‐
13 col and (in theory) should work when inserted between any compliant
14 tools. Ie. this can be used to monitor cache operation requests and
15 responses between applications and dc_client, or between dc_client and
16 dc_server.
17
18 This tool is still in early stages of development and is provided very
19 much ``as-is''. It is intended to be used by developers with access to
20 the source code - for now, most configurable behaviour of dc_snoop is
21 set in source code and can not be manipulated on the command-line.
22
24 -listen address
25 Configures the address on which dc_snoop should listen for incoming
26 connections. The syntax is that defined by the libnal API.
27
28 -server address
29 -connect address
30 These flags are identical, and specify the address dc_snoop should
31 transparently proxy all incoming connections to. For each connec‐
32 tion accepted by dc_snoop (on the address specified by -listen) a
33 corresponding connection is opened to the address specified by
34 these flags. When either connection is closed, dc_snoop will corre‐
35 spondingly close the other connection.
36
37 -h, -help, -?
38 Any of these flags will cause dc_snoop to display a brief usage
39 summary to the console and exit cleanly. Any other flags are
40 ignored.
41
43 This example demonstrates the use of dc_snoop to monitor communications
44 between an instance of dc_client and dc_server both running on the same
45 machine using only unix domain sockets. Suppose the tools are started
46 and tested using the following commands;
47
48 # Start services
49 dc_server -daemon -listen UNIX:/tmp/cacheserver
50 dc_client -deamon -listen UNIX:/tmp/cacheclient \
51 -server UNIX:/tmp/cacheserver
52 # Run some tests
53 dc_test -connect UNIX:/tmp/cacheclient
54
55 The following modification should be functionally equivalent (ignoring
56 the additional latency and overhead of dc_snoop's involvement) and
57 should generate a log file of all cache transactions to logfile. Note
58 the change to the -server flag in dc_client;
59
60 # Start services
61 dc_server -daemon -listen UNIX:/tmp/cacheserver
62 dc_client -deamon -listen UNIX:/tmp/cacheclient \
63 -server UNIX:/tmp/cachesnoop
64 # Start dc_snoop logging to logfile in the background
65 dc_snoop -listen UNIX:/tmp/cachesnoop \
66 -server UNIX:/tmp/cacheserver > logfile &
67 # Run some tests
68 dc_test -connect UNIX:/tmp/cacheclient
69
71 This program is incomplete and not at all configurable on the com‐
72 mand-line.
73
75 dc_client(1)
76 Distributed caching client proxy.
77
78 dc_server(1)
79 Distributed cache server.
80
81 distcache(8)
82 Overview of the distcache architecture.
83
84 http://www.distcache.org/
85 Distcache home page.
86
88 This toolkit was designed and implemented by Geoff Thorpe for Crypto‐
89 graphic Appliances Incorporated. Since the project was released into
90 open source, it has a home page and a project environment where devel‐
91 opment, mailing lists, and releases are organised. For problems with
92 the software or this man page please check for new releases at the
93 project web-site below, mail the users mailing list described there, or
94 contact the author at geoff@geoffthorpe.net.
95
96 Home Page: http://www.distcache.org
97
98
99
1001.4.5 2004.03.23 DC_SNOOP(1)