Research V4 development
[unix-history] / man / man7 / dpd.7
CommitLineData
21153b00
KT
1.th DPD VII 3/15/72
2.sh NAME
3dpd \*- spawn data phone daemon
4.sh SYNOPSIS
5.bd /etc/dpd
6.sh DESCRIPTION
7.it Dpd
8is the 201 data phone daemon.
9It is designed to submit jobs to
10the Honeywell 6070 computer via the GRTS
11interface.
12.s3
13.it Dpd
14uses the directory
15.it /usr/dpd.
16The file
17.it lock
18in that directory
19is used
20to prevent two daemons from becoming active.
21After the daemon has successfully set the lock,
22it forks and the main path exits, thus
23spawning the daemon.
24The directory is scanned for files
25beginning with
26.bd df.
27Each such file is submitted as a job.
28Each line of a job file must begin with a key
29character to specify what to do with the remainder
30of the line.
31.s3
32.lp +5 3
33\fBS\fR directs
34.it dpd
35to generate a unique snumb card.
36This card is generated by incrementing the first
37word of the
38file
39.it /usr/dpd/snumb
40and converting that to three-digit octal concatenated with
41the station ID.
42.s3
43.lp +5 3
44\fBL\fR specifies that the remainder of the line is to
45be sent as a literal.
46.s3
47.lp +5 3
48\fBB\fR specifies that the rest of the line
49is a file name.
50That file is to
51be sent as binary cards.
52.s3
53.lp +5 3
54\fBF\fR is the same as \fBB\fR except a form feed is prepended to the file.
55.s3
56.lp +5 3
57\fBU\fR specifies that the rest of the line
58is a file name.
59After the job has been transmitted,
60the file is unlinked.
61.s3
62.i0
63Any error encountered will cause the daemon to
64drop the call, wait up to 20 minutes and start over.
65This means that an improperly constructed
66\fIdf\fR file may cause the same job to be submitted
67every 20 minutes.
68.s3
69While waiting, the
70daemon checks to
71see that the
72.it lock
73file still exists.
74If it is gone,
75the
76daemon will exit.
77.sh FILES
78/dev/dn0,
79/dev/dp0,
80/usr/dpd/*
81.sh "SEE ALSO"
82opr(I)