User Guide

Appendix A – Included Application
Axis Communications AB does not provide support for application development of any kind. The
information here is provided "as is", and there is no guarantee that any of the examples shown
will work in your particular application.
Revision 0.91 June 2001 22
5.2.1 Built in commands
The shell includes a help command, which lists the available functions built in the
shell (see also Appendix B).
5.3 The image-buffer - bufferd
The application bufferd captures images and stores them on the ram-disk in a
FIFO-order, that is, the newest captured image overwrites the oldest.
By default initd starts a bufferd as a daemon. This daemon is listening for
messages on the socket /tmp/bufferdsocket. As a consequence it would not be
recommended to start several daemons as this would result in one daemon overwriting
what the other daemons writes.
The preferred way of using bufferd is depicted in the example below.
What happens when a call to bufferd is made is that the started process writes
messages to the socket /tmp/bufferdsocket and then dies.
Depending on which options are used when starting a buffer, bufferd starts one or two
processes for handling image capturing. These processes capture a number of images
according to the argument given.
5.3.1 Options
The valid parameters for bufferd are:
Option Meaning
-start Start a buffer.
-reset Remove a buffer.
-stop Stop a buffer.
-d
Start as a daemon.
This option should only be used when starting at start-up from
initd or when the first instance is to be started.
-buffername
<buffername>
The name of the buffer on which the options -start, -stop and -
reset should act.
bufferd will create a directory in /tmp named <buffername>
in which the images will be stored.
-uri <request-
string>
The request-uri.
Specification of the image-format as described in the HTTP-API
specification (pdf-document). The protocol should be 'FTP'
instead of 'htt
p
'. The document can be found on our web site