Cyc Administrator Handbook/Backup and Restore - Revision history

DavidWhitten: /* Dumping Units when using Transcript Servers */

2019-05-29T14:16:55Z

‎Dumping Units when using Transcript Servers

DavidWhitten: /* Dumping Units when using Transcript Servers */

2019-05-29T14:16:35Z

‎Dumping Units when using Transcript Servers

DavidWhitten: /* Using RAM disks under UNX /

2019-05-29T13:39:35Z

‎Using RAM disks under UN*X

DavidWhitten at 13:30, 29 May 2019

2019-05-29T13:30:49Z

DavidWhitten: /* The Basic Dump Command */

2019-05-29T13:26:33Z

‎The Basic Dump Command

DavidWhitten: /* The Basic Dump Command */

2019-05-29T13:26:12Z

‎The Basic Dump Command

DavidWhitten at 13:24, 29 May 2019

2019-05-29T13:24:26Z

DavidWhitten: /* Generate the KBS Partition */

2019-05-29T02:39:13Z

‎Generate the KBS Partition

DavidWhitten: /* Identifying a KB subset */

2019-05-29T02:38:49Z

‎Identifying a KB subset

DavidWhitten: /* Creating KB Subsets */

2019-05-29T02:38:11Z

‎Creating KB Subsets

@@ Line 23: / Line 23: @@
 == Dumping Units when using Transcript Servers ==
-{{To Be Completed}}
+{{To be completed}}
 == Dump Performance ==

@@ Line 23: / Line 23: @@
 == Dumping Units when using Transcript Servers ==
+{{To Be Completed}}
 == Dump Performance ==

@@ Line 34: / Line 34: @@
   # determine how much room is needed; assume KB number is 2100
-  # [[Cyc/Linux/command/cd|cd]]&nbrsp;[[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]]
+  # [[Cyc/Linux/command/cd|cd]]<nowiki>&nbsp;</nowiki>[[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]]
   cd ${CYC_BASE_DIR}

@@ Line 20: / Line 20: @@
   In addition, the process of dumping units files can perform various forms of cleanup and compaction, which is most interesting for situations of significant knowledge changes. The dump first performs a variety of clean ups, and then behave as DUMP-KB described above.
   The command is is (DUMP-STANDARD-KB path), where path is a slash terminated directory path that is interpreted relative to the [[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]].
-  The resulting units are directly usable by the CYC-LOAD-KB command, for example by editing the ${CYC_BASE_DIR}/init/jrtl-init.lisp startup file.
+  The resulting units are directly usable by the CYC-LOAD-KB command, for example by editing the [[Cyc/Linux/file/CYC_BASE_DIR/init/jrtl-init.lisp|'''${CYC_BASE_DIR}/init/jrtl-init.lisp''']] startup file.
 == Dumping Units when using Transcript Servers ==
   To Be Completed
 == Dump Performance ==
@@ Line 133: / Line 134: @@
 === Cleanly Rebuilding Preliminary into Final Units ===
-  This sequence of code steps will boot into the preliminary units KB, perform another round of standard cleanups, and then dump the final units to their directory path. Since the sequence explicitly loads the KB units, the code expects to be started without a KB (e.g. bin/run-cyc-no-init.sh -i init/cyc-init.lisp).
+  This sequence of code steps will boot into the preliminary units KB, perform another round of standard cleanups, and then dump the final units to their directory path. Since the sequence explicitly loads the KB units, the code expects to be started without a KB
 :(progn

@@ Line 11: / Line 11: @@
 == The Basic Dump Command ==
-  The basic command for dumping a set of units files is ([[Cyc/subl-function/dump-kb|DUMP-KB]] path), where path is a slash terminated directory path that is interpreted relative to the [[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]].
+  The basic [[SubL]] command for dumping a set of units files is ([[Cyc/subl-function/dump-kb|DUMP-KB]] path), where path is a slash terminated directory path that is interpreted relative to the [[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]].
   Since all network services have been stopped, the command must be issued either from the startup scripts, or at the read prompt.

@@ Line 15: / Line 15: @@
   Notice that dumping a KB always increments the KB number for the dumped units; loading them will result in a KB number higher by one.
-  The resulting units are directly usable by the CYC-LOAD-KB command, for example by editing the ${CYC_BASE_DIR}/init/jrtl-init.lisp startup file.
+  The resulting units are directly usable by the CYC-LOAD-KB command, for example by editing the [[Cyc/Linux/file/CYC_BASE_DIR/init/jrtl-init.lisp|'''${CYC_BASE_DIR}/init/jrtl-init.lisp''']] startup file.
 == The Clean-up Dump Command ==

@@ Line 8: / Line 8: @@
 == Dumping Units Files ==
   Akin to the data dump in an SQL server, the Cyc server can write a binary format of the knowledge that is suitable for backup and restore operations.
-  For the duration of a dump, the Cyc server must be segregated from all user interactions by disabling all network services; see the discussion of starting and stopping all TCP/IP services.
+  For the duration of a dump, the Cyc server must be segregated from all user interactions by disabling all network services; see the discussion of starting and stopping all TCP/IP services below.
 == The Basic Dump Command ==
-  The basic command for dumping a set of units files is (DUMP-KB path), where path is a slash terminated directory path that is interpreted relative to the ${CYC_BASE_DIR}.
+  The basic command for dumping a set of units files is ([[Cyc/subl-function/dump-kb|DUMP-KB]] path), where path is a slash terminated directory path that is interpreted relative to the [[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]].
   Since all network services have been stopped, the command must be issued either from the startup scripts, or at the read prompt.
@@ Line 19: / Line 19: @@
 == The Clean-up Dump Command ==
   In addition, the process of dumping units files can perform various forms of cleanup and compaction, which is most interesting for situations of significant knowledge changes. The dump first performs a variety of clean ups, and then behave as DUMP-KB described above.
-  The command is is (DUMP-STANDARD-KB path), where path is a slash terminated directory path that is interpreted relative to the ${CYC_BASE_DIR}.
+  The command is is (DUMP-STANDARD-KB path), where path is a slash terminated directory path that is interpreted relative to the [[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]].
   The resulting units are directly usable by the CYC-LOAD-KB command, for example by editing the ${CYC_BASE_DIR}/init/jrtl-init.lisp startup file.
@@ Line 30: / Line 30: @@
 == Using RAM disks under UN*X ==
-  The following example shows how to setup a RAM disk and use it for dumping units.
+  The following example linux shell script shows how to setup a RAM disk and use it for dumping units.
   # determine how much room is needed; assume KB number is 2100
+  # [[Cyc/Linux/command/cd|cd]]&nbrsp;[[Cyc/Linux/environment_variable/CYC_BASE_DIR|<nowiki>${CYC_BASE_DIR}</nowiki>]]
   cd ${CYC_BASE_DIR}
@@ Line 106: / Line 106: @@
   (progn
-  (set-kbs-definition-from-kbs-profile <kbs-profile-term>)
+  (set-kbs-definition-from-kbs-profile <nowiki><kbs-profile-term></nowiki>)
   (identify-kbs-forts-and-assertions))
@@ Line 117: / Line 117: @@
   This sequence of code steps will first identify the partition information and then serialize essential KB information into the partition file. The step also produces additional information about the utility of rules and the caching policies for SBHL, which are written (with standard names) to the partition directory provided.
- (progn
+:(progn
- (set-kbs-definition-from-kbs-profile <ProfileTerm>)
+::(set-kbs-definition-from-kbs-profile <nowiki><ProfileTerm></nowiki>)
- (make-kbs-partition <partition-dir> <partition-filename>))
+::(make-kbs-partition <nowiki><partition-dir></nowiki> <nowiki><partition-filename></nowiki>)
 === Expanding the KBS Partition into Preliminary Units ===
@@ Line 125: / Line 126: @@
   This sequence of code steps will load a partition, the rule utility information, and the SBHL caching policies into an empty KB; the code expects to be started from a CYC image without a KB (e.g. bin/run-cyc-no-init.sh -i init/cyc-init.lisp)
- (progn
+:(progn
- (load-partition-into-empty-kb <partition-dir> <partition-filename>)
+::(load-partition-into-empty-kb <nowiki><partition-dir></nowiki> <nowiki><partition-filename></nowiki>)
- (dump-standard-kb <pre-units-directory-path>))
+:: (dump-standard-kb <nowiki><pre-units-directory-path></nowiki>)
@@ Line 133: / Line 135: @@
   This sequence of code steps will boot into the preliminary units KB, perform another round of standard cleanups, and then dump the final units to their directory path. Since the sequence explicitly loads the KB units, the code expects to be started without a KB (e.g. bin/run-cyc-no-init.sh -i init/cyc-init.lisp).
- (progn
+:(progn
- (cyc-load-kb <pre-units-directory-path>)
+::(cyc-load-kb <nowiki><pre-units-directory-path></nowiki>)
- (kbs-image-cleanup)
+::(kbs-image-cleanup)
- (dump-standard-kb <final-units-directory-path>))
+::(dump-standard-kb <nowiki><final-units-directory-path></nowiki>)
 </noinclude>

@@ Line 84: / Line 84: @@
 == Identifying a KB subset ==
   The identification of KB subsets is done via the following set of KB vocabulary. Users are advised to refer to the comment assertions in the KB on these terms for their proper use.
-−
   #$KBSubsetProfile
-−
   #$kbsProfileRemoveAssertion
-−
   #$kbsProfileRemoveCollectionExtent
-−
   #$kbsProfileRemoveFORT
-−
   #$kbsProfileRemovePredicateExtent
-−
   #$kbsProfileRetainAssertion
-−
   #$kbsProfileRetainTerm
-−
   The basic process is to introduce a new term of type KBSubsetProfile, which is then associated via the relations mentioned above to assertions, terms, predicates or collection extents that are to be added or removed.

@@ Line 74: / Line 74: @@
 == Creating KB Subsets ==
-  CYC supports the ability of abstracting out a subset of knowledge that is useful in its own right, as a full-fledge knowledge base. These sets of knowledge are called KB subsets.
+  CYC supports the ability of abstracting out a subset of knowledge that is useful in its own right, as a full-fledged knowledge base. These sets of knowledge are called KB subsets.
   The process of creating a KB subsets consists of two key steps:

Cyc Administrator Handbook/Backup and Restore - Revision history

DavidWhitten: /* Dumping Units when using Transcript Servers */

DavidWhitten: /* Dumping Units when using Transcript Servers */

DavidWhitten: /* Using RAM disks under UN*X */

DavidWhitten at 13:30, 29 May 2019

DavidWhitten: /* The Basic Dump Command */

DavidWhitten: /* The Basic Dump Command */

DavidWhitten at 13:24, 29 May 2019

DavidWhitten: /* Generate the KBS Partition */

DavidWhitten: /* Identifying a KB subset */

DavidWhitten: /* Creating KB Subsets */

DavidWhitten: /* Using RAM disks under UNX /