+-+-+-+ Beginning of part 3 +-+-+-+ X Starting the Detached Process X X The BBoard detached process (running in Full mode) should be X started with the following command or a similar one: X X $ Run /Proc="BBoard_Daemon" /UIC=[BBOARD] /Priority=3 - X /Input=BBoard_Dir:Run_BBoard_Daemon.com - X /Output=BBoard_Dir:bboard.out - X /Error=BBoard_Dir:bboard.err - X /Priv=(TMPMBX,NETMBX,DETACH,SYSPRV,CMEXEC,CMKRNL) - X Sys$System:Loginout X X The file Run_BBoard_Daemon.COM performs a PURGE of certain files X and then RUNs BBOARD.EXE. This is required to establish a CLI X context, which LOGINOUT.EXE will do. X X Both Run_BBoard_Daemon.COM and a sample Start-BBoard.COM are X provided as part of the package to show examples of the required X setup. X X X Logical Names X X BBoard will look for the following logicals in the system logical X tables when it begins running. If it does not find a particular X logical, it will use the hard-coded defaults as shown. X X bboard_hook_name X X The name of the Jnet hook. This must also be the name of the X user account devoted to BBoard because that user is the X destination of incoming mail. X X Default: bboard X X bboard_dir X X The primary directory for BBoard. BBoard's X NOTES$NOTEBOOK.NOTE will appear in this directory, and the X .EXE should be placed here as well. X X Default: Sys$Sysdevice:[BBoard] X X - Page 5 - X BBOARD April 23, 1990 X`012 X X X X X X X X bboard_scratch_dir X X The directory used as a temporary space for BBoard's work X files and incoming mail. Normally, no files will be present X in this directory for any extended period of time. However, X sufficient space (and quota) must be available to accomodate X "peaks" in message arrival. X X Default: Sys$Sysdevice:[BBoard.Scratch] X X bboard_control_file X X The file specification from which BBoard will read its X control information. X X Default: BBoard_Dir:BBoard.CTL X X X Control File X X BBoard uses a control file (specified by the bboard_control_file X logical name) to control how it processes incoming mail. The X control file is an ASCII text file which can be created with EDT. X X The control file is divided into control sections. Each section X begins with a : line, where is the type of X control section that will follow. Comment lines are lines which X begin with an exclamation mark (!) and can be placed anywhere. X The control file may contain embedded tab characters with no ill X effects. X X Each of the control sections will be listed separately with a X full description and record layout. Any unaccounted space in each X record layout is filler space and is ignored when the control X file is read. X X A sample of each control section will follow the description of X the section. X X X Control Section - :lists X X This section contains all of the information that tells BBoard X what embedded text to search for to determine where a mail X message goes.`032 X Col Len Description X --- --- ----------------------------------------------------- X 1 10 Search Text. Once this text is found, the rest of this X :lists record will be used to post the note. This is X X - Page 6 - X BBOARD April 23, 1990 X`012 X X X X X X X also used as the keyword for any entry with keywords X enabled. X 12 20 Topic name. Used for new topics. Each new topic in X Notes will be described as " Postings for X " X 33 12 Conference user name. If this section is non-blank, X BBoard will change its username to this name before it X posts the entry. This will only work if Full mode X privileges are enabled. Also, conference user names X should be at least three characters to prevent possible X conflict with RSX naming conventions. X 46 1 Digest/Keyword flag. This character can be one of three X possibilities: X N Normal mail processing for this conference. X K Keywords are enabled for this conference. The X Search text will be used as a keyword for X each new note. This allows a SHOW NOTE to X show which LIST a particular note came from. X This feature would normally only be used if X multiple LISTs are being posted to the same X conference. X Y This conference is to be posted as a digest. X Digests are a special format whereby multiple X messages are contained in one mail message. X Enabling digest processing causes BBoard to X scan through a message to extract the X contained entries. X 48 1 Topic break Interval/Digest separator. This character X is a general purpose indicator whose use depends on X whether the Digest/Keyword flag enables digest X processing. X If normal mail processing is enabled, this character X indicates the posting interval. This controls how often X a new topic is written to the conference. In this case X the following are allowed: X W New topics on a weekly basis. A topic will X run from 12:00 AM Sunday through 11:59 PM of X the following Saturday. X M New topics on a monthly basis. A topic will X run through the last day of the month. X If digest processing is enabled, this character X references the :digests control section (see below) to X control how individual entries in the digest are X separated. Currently, the only separator character used X is the hyphen (-). X 50 1 Notes Conference Name. This is the actual conference X name used when Notes is started. We suggest a X consistent naming so users can readily determine if a X conference is local or a copy of a network list. One X possibility (used at St. Peter's) is to prefix the X X - Page 7 - X BBOARD April 23, 1990 X`012 X X X X X X X mailing list names with an "X-". X X :lists X MD4I Info-VAX InfoVAX N W X-Info-VAX X BITNEWS Bitnet Info K M X-Bitnet-Info X BITTECH Bitnet Info K M X-Bitnet-Info X ! Note: X ! BITNEWS and BITTECH will post to the same conference. Both X ! names must exist as keywords in the X-Bitnet-Info X ! conference. X FRAC-L Frac-L FracL N M X-Frac-L X