43BSDTahoe/new/notes/Samples/Read_me - annotate

Return to Read_me CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / new / notes / Samples

Annotation of 43BSDTahoe/new/notes/Samples/Read_me, revision 1.1.1.1

1.1 root 1: This directory contains files collected from various places
2: throughout the system. They are intended as examples (taken from real
3: life don't ya know) of how the files are intended to look.
4: I've tried to update this file as I diddle with things. Hopefully
5: any files which aren't listed in this file will enough documentation
6: within themselves to help you figure out where they belong. Most of
7: these files belong in the notesfile utility directory,
8: /usr/spool/notes/.utilities.
9:
10:
11: File What good is it
12: -------- ---------------------------
13: Read_me this file
14:
15: cronarch.sh shell file run "su" to the notesfile owner. This is
16: run several times weekly to archive or delete old notes.
17:
18: cronnet.sh shell file run "su" to the notesfile owner. This is
19: run occasionally (we are using 4 times daily) to
20: propogate new notes for USENET notesfiles. In our
21: situation, these notesfiles only see new traffic during
22: the evening. By running this less frequently, we
23: save a lot of cycles on our machines.
24:
25: cronlocal.sh shell file run "su" to the notesfile owner. This
26: one propogates local notesfiles across the network.
27: We separated the local updates from the USENET updates
28: so we could update local notesfiles hourly and
29: USENET notesfiles only a few times per day, centered
30: around our polling other sites.
31: This script is set up to talk to all of our local
32: sites and gathers the set of notesfiles to send to
33: each site from files, allowing easy changes to the
34: list of notesfiles sent around without modifying
35: the script itself. The same script is used on
36: all of our hosts -- we just make sure that the list
37: of notes to send to "yourself" is empty.
38:
39: crontab A copy of the added lines in /usr/lib/crontab
40: that we use for notes management.
41:
42: net.how /usr/spool/notes/.utilities/net.how - The file
43: used by "nfxmit" to get updates to other systems.
44: This is also used by "newsoutput" to figure out how
45: to get to Usenet.
46:
47: newsgroups Our mappings between notesfiles and newsgroups.
48: Lives in /usr/spool/notes/.utilities/newsgroups
49: [not terribly up to date -RBE 3/84]
50:
51: shorten Shell script to clean up the log files. Run at your
52: leisure. If you are hard up for disk space, run it often.
53:
54: syncnews C shell script provide by Brian Redman (harpo!ber)
55: which compares notesfiles and newsgroups to see
56: if any newsgroup does not have a matching notesfile.
57: This script does not use the "newsgroups" file to
58: alias between them. It is effective.
59:
60: sys A copy of /usr/lib/news/sys (for A news: /usr/spool/news/.sys)
61: This shows how to get the news forwarded into notesfiles.
62:
63: Archive-into An example of the mapping file between active and archive
64: notesfiles. I'm not using this feature too often, but
65: this file gives you an idea of what is expected. The
66: final resting place for this file is
67: /usr/spool/notes/.utilities/net.aliases/Archive-into
68:
69: access-template This file contains modifications to the normal
70: access list given to newly created notesfiles. It is
71: handy to ensure that whoever manages the notesfile
72: data base can access notesfiles from his own account
73: in addition to the "notes" account. It can also
74: be used to restrict access to new notesfiles.
75: For more information on the format of this file, see
76: the man page for nfaccess(8).
77:
78: avail.notes A copy of our "avail.notes" file. This describes
79: the available notesfiles. This only contains the
80: notesfiles that the administrator wishes to advertise.
81: We list a number of our local notesfiles and then
82: append the monthly USENET newsgroup listing.
83:
84: short.names This is a list of newsgroups which are longer than
85: 14 characters. On non-4.2 BSD systems, a notesfile
86: name is limited to 14 characters [4.2 gets to use 255].
87: If you have a 4.2 BSD system with long names and a
88: neighbor with the short names, the following scenario
89: can take place:
90:
91: you get news into "net.unix-wizards" and
92: send it to your non-4.2 neighbor. He promptly
93: truncates it to "net.unix-wizar". When the
94: time comes for him to send back to you, it shows
95: up on your machine in "net.unix-wizar".
96:
97: What we have done at UIUC is use symbolic links to make
98: "net.unix-wizar" point at "net.unix-wizards". The
99: short.names file allows us to send "net.*" and use
100: the ! exclusion feature to remove references to the
101: links such as "net.unix-wizar". The list is probably
102: not quite in synch with the current USENET newsgroups.

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.