forked from Kampbell/isode-8.0
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathisode-gen.8
1452 lines (1452 loc) · 37.6 KB
/
isode-gen.8
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
.TH ISODE-GEN 8 "19th June 1992"
.ds VD isode\-8.0
.ds VN 8.0
.\" $Header: /xtel/isode/isode-master/RCS/isode-gen.8,v 9.0 1992/06/16 13:01:55 isode Rel $
.\"
.\"
.\" $Log: isode-gen.8,v $
.\" Revision 9.0 1992/06/16 13:01:55 isode
.\" Release 8.0
.\"
.\" Revision 9.0 1992/06/16 12:05:01 isode
.\" Release 8.0
.\"
.\"
.SH NAME
isode\-gen \- generating the ISO Development Environment
.SH "READ THIS"
This documentation describes how to configure, generate, and install the
ISO Development Environment.
.PP
Acquisition, use, and distribution of this module and related
materials are subject to the restrictions of a license agreement.
Consult the Preface in the \fIUser's Manual\fR for the full terms of this
agreement.
.PP
You will probably want to read over this entire document first,
before typing any commands;
e.g., there are optional components described later on that require
additional settings in the configuration file.
.PP
There is an ISODE discussion group
\*([email protected]\*(rq.
If you want to subscribe to the ISODE discussion group,
drop a note to \*([email protected]\*(rq.
.SH SYNOPSIS
.sp
.in +.5i
.nf
% cd \*(VD
% cp config/\fIsystem\fR.h h/config.h
% cp config/\fIsystem\fR.make config/CONFIG.make
% cp config/*.local support/
% ./make everything
# ./make inst\-everything
.fi
.in -.5i
.sp
.SH DESCRIPTION
This is a description of how one can bring up the ISODE.
It is assumed that you have super\-user privileges in order to (re\-)install
the software.
Super\-user privileges are not required to configure or generate this
software.
.PP
The distribution tape contains the hierarchy for the \fB\*(VD\fR directory.
Bring the sources on\-line by changing to a directory for local sources and
running tar, e.g.,
.sp
.in +.5i
.nf
% cd /usr/src/local/
% tar x
% cd \*(VD
.fi
.in -.5i
.sp
.SH CONFIGURATION
First, go to the \fBconfig/\fR directory.
.sp
.in +.5i
.nf
% cd config
.fi
.in -.5i
.sp
.PP
Select the Makefile and include-file skeletons which most closely match
your system.
The current choices are:
.sp
.in +.5i
.nf
.ta \w'sys52-exos 'u
.ne 4
\fIfile\fR \fIconfiguration\fR
aix AIX 3.2
apollo Apollo
aux A/UX release 2.0.1
bsd42 generic 4.2BSD UNIX
bsd43 generic 4.3BSD UNIX
bsd43\-rt RT/PC with 4.3BSD
bsd44 4.4BSD UNIX with OSI
ccur Concurrent RTU 6.0
hpux HP\-UX
mips MIPS RISC/OS
osx Olivetti LSX 30xx
ros Ridge Operating System
solbourne Solbourne
sunlink3 SunOS release 3 with SunLink OSI/X.25 release 5.2
sunlink4 SunOS release 4 with SunLink OSI/X.25 release 6.0
sunnet7 SunOS release 4 with SunNet OSI release 7.0
sunnet7x SunOS release 4 with SunNet X.25 release 7.0
sunos3 SunOS release 3
sunos4 SunOS release 4
sunos4-1 SunOS release 4.1
sys52\-exos SVR2 UNIX with EXOS
sys52\-rt RT/PC with AIX
sys52\-sun SVR2 UNIX emulation on SunOS release 3
sys52\-win SVR2 UNIX with WIN/TCP
sys53 generic SVR3
sys54 generic SVR4
ultrix Ultrix 3.1
.re
.fi
.in -.5i
.sp
The makefile skeleton has the extension \fB.make\fR,
whereas the include\-file skeleton has the extension \fB.h\fR.
.SS MAKEFILE
Copy the makefile skeleton of your choice to \fBpickle.make\fR,
where \*(lqpickle\*(rq is the name of your system.
Now edit this file to set the following \fImake\fR variables:
.sp
.in +.5i
.nf
.ta \w'MANOPTS 'u +\w'/usr/include/isode/ 'u
.ne 8
\fIvariable\fR \fIdefault\fR \fIspecifies\fR
OPTIONS options to \fIcc\fR and \fIlint\fR (e.g., -I../h)
LSOCKET libraries to link in (e.g., -lcci)
BINDIR /usr/local/bin/ where to install user programs
SBINDIR /usr/etc/ where to install administrator
programs
ETCDIR /usr/etc/ where to install administrator files
LOGDIR /usr/tmp/ where to install log files
INCDIR /usr/include/isode/ where to install include files
LIBDIR /usr/lib/ where to install object libraries
LINTDIR /usr/lib/lint/ where to install lint libraries
SYSTEM directs how to create loader libraries
MANDIR /usr/man/ where to install man pages
MANOPTS see compat/inst-man.sh for details
.re
.fi
.in -.5i
.sp
\fBNOTE THAT ALL THESE DIRECTORIES MUST BE ABSOLUTE PATH NAMES
(i.e., start and end with a `/')\fR.
.PP
Finally,
.sp
.in +.5i
.nf
ln pickle.make CONFIG.make
.fi
.in -.5i
.sp
(yes, that's \*(lqCONFIG\*(rq in uppercase and \*(lqmake\*(rq in lowercase).
Both of these files are in the \fB\*(VD/config/\fR directory.
This latter file is the one which the software uses to configure itself
during generation.
.SS INCLUDE\-FILE
Copy the include\-file skeleton of your choice to \fBpickle.h\fR,
where \*(lqpickle\*(rq is the name of your system.
Now add any additional definitions you like (usually none).
Consult the file \fBconfig/OPTIONS\fR for a list.
.PP
Now:
.sp
.in +.5i
.nf
ln pickle.h ../h/config.h
.fi
.in -.5i
.sp
This latter file is the one which the software uses to configure itself
during generation.
.SS "ALIASES DATABASE"
Typically,
sites run with the default aliases database used
by the OSI directory.
In this case,
simply copy the default local configuration file to the \fBsupport/\fR
directory:
.sp
.in +.5i
.nf
% cp aliases.local ../support/
.fi
.in -.4i
.sp
If you have local modifications you wish to make,
either copy in your own file or edit the file
\fBsupport/aliases.local\fR as appropriate.
.SS "SERVICES DATABASE"
Typically,
sites run with the default services database.
In this case,
simply copy the default local configuration file to the \fBsupport/\fR
directory:
.sp
.in +.5i
.nf
% cp services.local ../support/
.fi
.in -.4i
.sp
If you have local modifications you wish to make,
either copy in your own file or edit the file
\fBsupport/services.local\fR as appropriate.
.SS "ENTITIES DATABASE"
Typically,
sites run with the default application entity database used
by the stub\-directory service.
However,
once things are running,
sites should use the OSI Directory to keep track of application entities.
So,
to begin,
simply copy the default local configuration file to the \fBsupport/\fR
directory:
.sp
.in +.5i
.nf
% cp entities.local ../support/
.fi
.in -.5i
.sp
If you have local modifications you wish to make,
either copy in your own file or edit the file
\fBsupport/entities.local\fR as appropriate.
.PP
In particular,
if you are using SunNet OSI,
it will be necessary to put an entry in your
\fBsupport/entities.local\fR file of the form:
.sp
.in +.5i
myhost\0default\0\01.17.4.1.0\0\0#1/NS+mynsap
.in -.5i
.sp
where \*(lqmyhost\*(rq is the name of the local machine,
and \*(lqmynsap\*(rq is the NSAP of the local machine.
For SunNet OSI 7.0 the NSAP is most easily determined by running
.sp
.in +.5i
.nf
% /usr/sunlink/osi/etc/osirstat -n | grep ^DA
.fi
.in -.5i
.sp
provided that the SunNet OSI osi.routed program is running. For
earlier SunLink OSI releases you can run
.sp
.in +.5i
.nf
% cd others/osilookup
% ./make
% xosilookup localhost CLIENT
.fi
.in -.5i
.sp
providing that the SunLink OSI file \fB/etc/sunlink/osi/hosts\fR
has an entry defining the service for \*(lqlocalhost\*(rq called
\*(lqCLIENT\*(rq.
(Note that in releases earlier than SunLink OSI 6.0,
the file is called \fB/usr/etc/osi.hosts\fR)
Note that this entry is mandatory if you are running SunLink OSI
release 5.2 or greater.
.PP
One further note for users of a release earlier then 7.0 of SunLink OSI:
if you intend to run the standard SunLink OSI listener (osi.netd),
then you must change the TSEL used by \fItsapd\fR when it listens.
This is done in two steps:
First,
in \fBsupport/entities.local\fR,
change your entry to read as:
.sp
.in +.5i
myhost\0default\0\01.17.4.1.0\0\0#2/NS+mynsap
.in -.5i
.sp
Second,
in \fBsupport/services.local\fR,
add a line that reads as:
.sp
.in +.5i
tsap/session\0\0#2\0\0tsapd-bootstrap
.in -.5i
.sp
which overrides the default TSEL in the \fBsupport/services.db\fR file.
.SS "MACROS DATABASE"
Typically, sites run with the default macros database.
In this case,
simply copy the default local configuration file to the \fBsupport/\fR
directory:
.sp
.in +.5i
.nf
% cp macros.local ../support/
.fi
.in -.5i
.sp
If you have local modifications you wish to make,
either copy in your own file or edit the file
\fBsupport/macros.local\fR as appropriate.
.SS "OBJECTS DATABASE"
Typically, sites run with the default objects database.
In this case,
simply copy the default local configuration file to the \fBsupport/\fR
directory:
.sp
.in +.5i
.nf
% cp objects.local ../support/
.fi
.in -.4i
.sp
If you have local modifications you wish to make,
either copy in your own file or edit the file
\fBsupport/objects.local\fR as appropriate.
.SH GENERATION
Go to the \fB\*(VD\fR directory
.sp
.in +.5i
.nf
% cd ..
.fi
.in -.5i
.sp
Now reset the dates of the
configuration files for the system.
This is done only once per source-tree:
.sp
.in +.5i
.nf
% ./make once-only
.fi
.in -.5i
.sp
then generate the basic system.
.sp
.in +.5i
.nf
% ./make
.fi
.in -.5i
.sp
If you are using SunOS,
do not use the \fImake\fR program supplied with the SunPro package.
It is not, contrary to any claims, compatible with the standard
\fImake\fR facility.
Further,
note that if you are running a version of SunOS 4.0 prior to release 4.0.3,
then you may need to use the \fImake\fR program found in \fB/usr/old/\fR,
if the standard \fImake\fR your are using is the SunPro \fImake\fR.
In this case,
you will need to put the old, standard \fImake\fR in \fB/usr/bin/\fR,
and you can keep the SunPro \fImake\fR in \fB/bin/\fR.
.PP
If you are using SVR3,
then you will probably have to type this command before starting the
compilation:
.sp
.in +.5i
.nf
% ulimit 32768
.fi
.in -.5i
.sp
Similarly,
you may need to increase the stacksize limitation on other systems.
For example,
some users of the RT, report needing to use
.sp
.in +.5i
.nf
% limit stacksize 16m
.fi
.in -.5i
.sp
in order to get FTAM to fully compile.
.PP
The \fImake\fR command from the top-level directory
will cause a complete generation of the system.
If all goes well, proceed with the installation.
If not, complain, as there \*(lqshould be no problems\*(rq at this step.
Some files while compiling may produce a
.sp
.in +.5i
.nf
warning: statement not reached
.fi
.in -.5i
.sp
or a
.sp
.in +.5i
.nf
type ObjectDescriptor: Warning: Can't find file DSE.ph failed
.fi
.in -.5i
.sp
message.
This is normal.
Sometimes when building a loader library, you might see several
.sp
.in +.5i
.nf
ranlib: warning: ../libisode.a(aetdbm.o): no symbol table
.fi
.in -.5i
.sp
messages.
This is also normal.
You might also see a few messages like:
.sp
.in +.5i
.nf
*** Error code 1 (ignored)
.fi
.in -.5i
.sp
This is also normal.
As a rule, unless \fImake\fR says something like
.sp
.in +.5i
.nf
*** Error code 1
.fi
.in -.5i
.sp
or perhaps
.sp
.in +.5i
.nf
Exit
.fi
.in -.5i
.sp
then everything is going just fine!
.SH TESTING
Some directories may have a resident test program,
e.g., in the \fBpsap/\fR directory, there is a program called \fIpsaptest\fR.
These programs are for internal testing only,
and are not for use by \*(lqmere mortals\*(rq.
If you want to test things,
after installation run \fIisode\-test\fR (see the \fBUSER PROGRAMS\fR section).
.SH INSTALLATION
You will need to be the super\-user to install the software.
Note that installing the software from an NFS-mounted partition
requires that you perform the installation as the super-user on the
\fItarget\fR system after changing to the source directory on the
\fIsource\fR system.
.PP
In the directions that follow,
reference is made to some of the directories defined in the
\fBCONFIG.make\fR file.
You should substitute in the correct value,
for example,
if the expression
.sp
.in +.5i
.nf
$(SBINDIR)tsapd
.fi
.in -.5i
.sp
and if SBINDIR is defined as \fB/usr/etc/\fR in the \fBCONFIG.make\fR
file,
then you should type
.sp
.in +.5i
.nf
/usr/etc/tsapd
.fi
.in -.5i
.sp
instead.
.PP
There are two kinds of activities:
once\-only activities that you perform the first time the software is
installed;
and each\-time activities that you perform every time the software is
installed.
.PP
The first once\-only activity is to verify that the \fItsapd\fR daemon will be
run when the machine goes multi\-user.
On Berkeley UNIX systems, add these lines to the \fB/etc/rc.local\fR file:
.sp
.in +.5i
.nf
if [ \-f $(SBINDIR)tsapd ]; then
$(SBINDIR)tsapd >/dev/null 2>&1 &
(echo \-n ' tsap') > /dev/console
fi
.fi
.in -.5i
.sp
On other systems, a similar procedure is followed.
For example,
on systems derived from AT&T UNIX,
the file \fB/etc/rc2\fR script might be edited.
.PP
Once you are familiar with the system,
you will likely want to run the OSI Directory and use another program,
\fIiaed\fR to invoke local services.
The section \fBDIRECTORY SERVICES\fR discusses this in greater detail.
(However,
if this is your first time,
don't skip ahead.)
.PP
The next once\-only activity is to verify that systems with a native
\fB/etc/services\fR file contain an entry for the tsap service
(if you have configured the ISODE to run over TCP).
If not,
add the line:
.ta \w'iso-tsap\0\0\0\0'u
.sp
.in +.5i
.nf
tsap 102/tcp
.fi
.in -.5i
.sp
to the \fB/etc/services\fR file. Alternatively, some systems may have
a definition of the form
.sp
.in +.5i
.nf
iso-tsap 102/tcp
.fi
.in -.5i
.sp
which is also acceptable. If your system does not have such a file,
the software automatically compensates for this.
.PP
Next,
on Berkeley UNIX systems,
add a line to the \fB/usr/lib/crontab\fR file to invoke a
shell-script that will re-cycle the log files.
Usually, the line you add looks something like this:
.sp
.in +.5i
.nf
0 4 * * * su daemon < $(SBINDIR)isologs
.fi
.in -.5i
.sp
which says that the shell-script $(SBINDIR)isologs should be invoked at 4am
each morning.
On other systems, a similar procedure is followed.
For example,
on systems derived from AT&T UNIX,
the file \fB/usr/spool/cron/crontabs/root\fR might be edited followed
by the command
.sp
.in +.5i
.nf
% crontab root
.fi
.in -.5i
.sp
.PP
There are two each\-time activities:
.sp
.in +.5i
.nf
# ./make inst\-all
.fi
.in -.5i
.sp
which does the installation.
This command will try to build all the directories you have specified,
using \fImkdir\fR.
This means that the parent of each of these directories must exist for the
the \fImkdir\fR to succeed.
.PP
The second each\-time activity,
is that if you are already running the ISODE,
then you will need to kill and restart the \fItsapd\fR\0(8c) daemon,
otherwise incoming connections will not be initialized correctly.
Otherwise, start the daemon now.
From the \fICShell\fR, the command might be:
.sp
.in +.5i
.nf
# $(SBINDIR)tsapd >& /dev/null
.fi
.in -.5i
.sp
The daemon will automatically detach.
If you do not redirect the daemon's standard\-error,
then it will not detach, instead printing messages as to what actions it
is taking.
.PP
That's about it. This will install everything.
To clean-up the source tree as well,
then use:
.sp
.in +.5i
.nf
% ./make clean
.fi
.in -.5i
.sp
at this point.
Note that if you are planning on generating or installing FTAM or VT
or QUIPU (described below),
then you should not clean-up the source tree until after you are
finished dealing with these.
.PP
If your system is configured for TCP/IP,
and you are not already running an SNMP agent,
then you are \fBURGED\fR to immediately install the SNMP agent
distributed with the ISODE.
Consult the \fBNETWORK MANAGEMENT\fR section below.
.PP
Finally,
if you are interested in discussing the ISODE with others running the software,
drop a note to the Internet mailbox
\*(lqISODE\[email protected]\*(rq,
and ask to be added to the \*([email protected]\*(rq list.
.SH TAILORING
If you create a file called \fB$(ETCDIR)isotailor\fR,
then you can customize the behavior of the programs which use the
ISODE when they start.
Consult the \fBsupport/isotailor.5\fR file for further information.
.SH "USER PROGRAMS"
By default,
two services are installed.
.PP
The first service,
having programs \fIisoc\fR and \fIisod\fR,
is used to test out the installation of the ISODE on your system:
.sp
.in +.5i
.nf
% ./make test
.fi
.in -.5i
.sp
which runs the \fIisode\-test\fR script.
.PP
The second service,
having programs \fIimisc\fR and \fIros.imisc\fR,
is a small demo service supporting things like \fIfinger\fR, \fIwho\fR and
so forth.
.PP
There are additional programs in the \fBothers/\fR directory.
These aren't integral parts of the system and assume that the ISODE is already
installed.
Use at your own discretion.
.SH "REGISTERING OSI APPLICATION SERVICES"
.PP
Earlier releases of the ISODE relied on static tables to keep track of
the OSI application services offered on an end-system.
This is a problematic exercise in keeping local and remote tables synchronized.
In this release of the ISODE,
the OSI Directory can be used to manage this information,
thereby automating the synchronization process.
.SS "Preparation"
.PP
Once you have installed the ISODE, you must bring up a DSA.
The procedures for doing this varies, depending on your location;
consult the section "Setting up an Initial DSA" in Volume 5 of the
\fIUser's Manual\fR.
.PP
You should also configure the \fB$(ETCDIR)ufnrc\fR file to reflect your
local Directory Tree.
Details are given at the head of the stub \fBufnrc\fR
file installed during the ISODE installation phase.
.PP
Once your DSA is running,
you should build the DMD for your organization.
Underneath the entry for your organization,
you should select an area where your end-system's application entities
will reside in the DIT.
For example,
the OSI application services available in PSI's Santa Clara office
reside somewhere under:
.sp
.in +.5i
.nf
c=US
@o=Performance Systems International
@ou=Research and Development
@ou=Santa Clara
.fi
.in -.5i
.sp
Note that this area may very well be different than the value of the
\*(lqlocal_DIT\*(rq in your dsaptailor file.
In general,
all the end-systems at a site will have the same "local_DIT" value,
but each of those end-systems offering OSI application services will
place those services at a different portion in the DIT
(usually somewhere underneath the \*(lqlocal_DIT\*(rq value).
.PP
By convention, all the OSI application services offered by a given
end-system are placed in the same location in the DIT, under an
applicationProcess entry with the short name of the end-system,
e.g., \*(lqcn=cheetah\*(rq.
So, using the example above, the entry
.sp
.in +.5i
.nf
c=US
@o=Performance Systems International
@ou=Research and Development
@ou=Santa Clara
@cn=cheetah
.fi
.in -.5i
.sp
would contain all the entries of interest.
.SS "Once-only Installation"
.PP
The \fIbootsvc\fR script will generate a shell script that will create
an applicationProcess entry and then an entry for each of the OSI
services provided by the ISODE.
So,
you must first select the RDN for the applicationProcess entry.
.PP
Run \fIbootsvc\fR to create a script:
.sp
.in +.5i
.nf
% support/bootsvc <<aP-name>> > run.sh
.fi
.in -.5i
.sp
e.g.,
.sp
.in +.5i
.nf
% support/bootsvc cheetah > run.sh
.fi
.in -.5i
.PP
Note that the first line of this script is used to define the network
address where \fIiaed\fR listens for incoming connections.
By default,
only the address for the Internet community (RFC1006) is set.
If the end-system is configured for other OSI communities,
then this line should be changed accordingly, e.g.,
.sp
.in +.5i
.nf
A="Internet=`hostname`|NS+aabbcc"
.fi
.in -.5i
.PP
Next,
start \fIdish\fR in the background,
bind as the manager,
move to the location in the DIT where the services are to be
registered and run the script,
e.g.,
.sp
.in +.5i
.nf
% setenv DISHPROC "127.0.0.1 `expr $$ + 32768`"
% bind -u <<DN of DSA Manager>>
% moveto "ou=Research and Development@ou=Santa Clara"
% sh run.sh
.fi
.in -.5i
.sp
.PP
Following this,
you need to arrange for \fIiaed\fR rather than \fItsapd\fR to run when
the machine goes multi\-user.
On Berkeley UNIX systems, replace these lines to the \fB/etc/rc.local\fR file:
.sp
.in +.5i
.nf
if [ \-f $(SBINDIR)tsapd ]; then
$(SBINDIR)tsapd >/dev/null 2>&1 &
(echo \-n ' tsap') > /dev/console
fi
.fi
.in -.5i
.sp
with:
.sp
.in +.5i
.nf
if [ \-f $(SBINDIR)iaed ]; then
$(SBINDIR)iaed -D 'ou=Research and ...@cn=services' >/dev/null 2>&1 &
(echo \-n ' iae') > /dev/console
fi
.fi
.in -.5i
.sp
On other systems, a similar procedure is followed.
.PP
When \fIiaed\fR starts,
it will connect to the Directory,
find the services contained therein,
and start listening as appropriate.
.PP
Finally,
when the Directory software was installed,
this included a program called \fIdased\fR.
If you have not already done so,
edit the \fB$(ETCDIR)isotailor\fR file to have these two lines:
.sp
.in +.5i
.nf
ns_enable: on
ns_address: Internet=domain-name+17006
.fi
.in -.5i
.sp
where \*(lqdomain-name\*(rq is the DNS name or IP-address of the
machine which is running \fIdased\fR.
This can be a different machine than the one running the DSA,
but it's probably best to have the local DSA and \fIdased\fR running
on the same machine.
.PP
Next,
arrange for \fIdased\fR to be started when the machine goes multi-user.
On Berkeley UNIX systems, add these lines to the \fB/etc/rc.local\fR file:
.sp
.in +.5i
.nf
if [ \-f $(SBINDIR)dased ]; then
$(SBINDIR)dased >/dev/null 2>&1 &
(echo \-n ' dase') > /dev/console
fi
.fi
.in -.5i
.sp
On other systems, a similar procedure is followed.
.PP
When \fIdased\fR starts,
it will listen for incoming connections from initiator ISODE programs.
(By default,
the initiator programs aren't loaded with the user-friendly
nameservice and the DAP, owing to the code size--instead, they talk to
\fIdased\fR.)
.PP
For your other systems,
edit the \fB$(ETCDIR)isotailor\fR file to have these two lines:
.sp
.in +.5i
.nf
ns_enable: on
ns_address: Internet=domain-name+17006
.fi
.in -.5i
.sp
where \*(lqdomain-name\*(rq is the DNS name or IP-address of the
machine which is running \fIdased\fR.
.PP
To test the system:
.sp
.in +.5i
.nf
% isode-test -iaed
.fi
.in -.5i
.sp
If all goes well,
users should be able to type things such as
.sp
.in +.5i
.nf
% ftam cheetah,sc,psi,us
.fi
.in -.5i
.sp
and \*(lqthe right thing\*(rq will happen
(i.e.,
local users can access remote services,
even if they have not been entered into the entities database).
.SS "Adding New Services"
.PP
The installation procedures need be performed only once.
If you decide to disable a service,
simply remove the corresponding entry from the Directory.
To add a new service,
see the Section \*(lqDefining New Services\*(rq in the \fIUser's Manual\fR.
.SH "FTAM/FTP gateway"
.PP
Because the FTAM/FTP gateway is meant to appear as an FTAM entity,
the entry for this service must be placed in a different portion of
the DIT than the regular FTAM service.
As such, the \fIbootsvc\fR script will not install this service.
.PP
Hence,
if you wish to run such a service, you will have to install it manually.
The entry might be something like this:
.sp
.in +.5i
.nf
objectClass= top & quipuObject &\e
applicationEntity & iSODEApplicationEntity
cn= <<whatever you want>>
presentationAddress= <<unique transport selector>>/<<end-system's NSAP>>
supportedApplicationContext= iso ftam
acl=
execVector= iso.ftam-ftp
.fi
.in -.5i
.sp
Look in your part of the Directory to see some examples of what these
entries look like. The are some scripts described in
\fIothers/quipu/tools/scripts/READ-ME\fR
which can be used to maintain such entries.
.SH "FILE TRANSFER, ACCESS AND MANAGEMENT"
In addition,
if you are running the ISODE on a Berkeley or AT&T System V UNIX system,
then there is also an implementation of the ISO FTAM.
FTAM, which stands for File Transfer, Access and Management,
is the OSI file service.
The implementation provided is fairly complete in the context of
the particular file services it offers.
It is a minimal implementation in as much as it offers only four core
services: transfer of text files,
transfer of binary files,
directory listings,
and file management.
.PP
To generate FTAM, go to the \fB\*(VD\fR directory and type:
.sp
.in +.5i
.nf
% ./make all-ftam
.fi
.in -.5i
.sp
.PP
This will cause a complete generation of the FTAM libraries and programs.
If all goes well, proceed with the installation.
If not, complain as there \*(lqshould be no problems\*(rq at this step.
.PP
You will need to be the super-user to install FTAM:
.sp
.in +.5i
.nf
# ./make install\-ftam
.fi
.in -.5i
.sp
That's about it.
This will install everything and then clean\-up the source tree.
Note that if you are planning on generating or installing the FTAM/FTP
gateway (described below),
then you should not clean-up the source tree until after you are
finished dealing with the gateway.
In this case,
or if you just want an installation and no clean\-up, then use:
.sp
.in +.5i
.nf
# ./make inst\-ftam
.fi
.in -.5i
.sp
instead.
.SH "FTAM/FTP GATEWAY"
In addition,
if you are running the ISODE on a Berkeley or AT&T System V UNIX system,
there is also an implementation of an FTAM/FTP application gateway.
The gateway is actually two programs:
one which acts as an ftam responder and an ftp client,
and the other which acts as an ftp server and an ftam initiator.
Note that the gateway currently resides at a different location
than the standard FTAM responder and FTP server.
(This may be corrected in a future release.)
Read the manual entries for \fIftamd-ftp\fR\0(8c) and
\fIftpd-ftam\fR\0(8c) for the details.
.PP
To generate the FTAM/FTAM gateway, go to the \fB\*(VD\fR directory and type:
.sp
.in +.5i
.nf
% ./make all-ftam-ftp
.fi
.in -.5i
.sp
.PP
This will cause a complete generation of the gateway.
If all goes well, proceed with the installation.
If not, complain as there \*(lqshould be no problems\*(rq at this step.
.PP
You will need to be the super-user to install the FTAM/FTP gateway:
.sp
.in +.5i
.nf
# ./make install\-ftam-ftp
.fi
.in -.5i
.sp
This will install everything and then clean\-up the source tree.
If you just want an installation and no clean\-up, then use:
.sp
.in +.5i
.nf