From c6b34739b69f76654000071ab27c565b839e2942 Mon Sep 17 00:00:00 2001 From: Linus Tolke Y <linus@lysator.liu.se> Date: Sat, 24 Aug 1991 11:51:46 +0000 Subject: [PATCH] Fixad med ny formatering. Kollad med gs. --- doc/man/lyskom.5 | 55 +++++++++++++++++++++++++++++++------------ doc/man/man5/lyskom.5 | 55 +++++++++++++++++++++++++++++++------------ doc/man/man5/ramkom.5 | 55 +++++++++++++++++++++++++++++++------------ 3 files changed, 120 insertions(+), 45 deletions(-) diff --git a/doc/man/lyskom.5 b/doc/man/lyskom.5 index 1cb31d31e..e507faa7f 100644 --- a/doc/man/lyskom.5 +++ b/doc/man/lyskom.5 @@ -1,5 +1,5 @@ -.\" $Id: lyskom.5,v 1.2 1991/08/24 11:24:53 linus Exp $ -.\" $Date: 1991/08/24 11:24:53 $ +.\" $Id: lyskom.5,v 1.3 1991/08/24 11:51:46 linus Exp $ +.\" $Date: 1991/08/24 11:51:46 $ .TH ramkom 5 "August 24, 1991" .SH NAME ramkom - LysKOM @@ -9,9 +9,9 @@ format .B /usr/lyskom/db/ramkomd-* .br and -.PP -.B /usr/lyskom/etc/pid .br +.B /usr/lyskom/etc/pid +.PP .B #include <lyskom/kom-types.h> .SH DISCLAIMER The @@ -64,13 +64,13 @@ The different statuses types are and .B text .BR statuses . -I consider them as structs but in this file they are not saved as -structs but every element is save as a ascii string. Strings are -saved as holerith strings. The field of the struct is not even saved -in the same order as in the struct. The order they are saved in is -described below. +These are in a struct in the include file but in this file they are +not saved as structs but every element is saved as a ascii string. +Strings are saved as holerith strings. The field of the struct is not +even saved in the same order as in the struct. +Their order in the database is followed below. .PP -An array of things is reprecented in the database by a number telling +An array of things is represented in the database by a number telling how many elements there are in the array and the either a .B * in the case no elements or a @@ -82,7 +82,7 @@ followed by all the elements and a finishing This contains all information for a conference. A conference is a object that recieves texts. .TP 15 -.B Name +.I Name Name of the conference saved as a holerith string. .TP .I Member list @@ -126,7 +126,9 @@ box of the creator. .I Permitted submitters This is the number of the conference whose members are allowed to submit texts to this conference. If this is 0 (the default) all -persons i LysKOM are allowed to submit. +persons i +.B LysKOM +are allowed to submit. .TP .I Super conference This is a number of a conference that comments to articles should be @@ -174,7 +176,7 @@ element in the array is a text number and a mark number. .I Membership Here is the information about which conferences the person is member in. Its an array where every element is of the type -.I Membership +.B Membership (See below). .TP .I Last login @@ -185,7 +187,9 @@ Number of the text being the persons user area. If there is no user area this is 0. .TP .I Total time present -Time in LysKOM in seconds. +Time in +.B LysKOM +in seconds. .TP .I Sessions Number of logins made for that person. @@ -261,9 +265,30 @@ An array containing the texts that we have read after the .I Last text .IR read . This is necessary because its possible to read in any order. +.SH FILES +.TP 20 +.IB database-directory /db/ramkomd-data +File with all the elements and pointers. +.TP +.IB database-directory /db/ramkomd-texts +File with the texts. +.TP +.IB database-directory /etc/pid +File with the pid of the lyskom-process. +.TP +.IB database-directory /db/ramkomd-backup +Backup file with all data. +.SH "SEE ALSO" +.BR ramkomd (8), +.BR dbck (8) .SH BUGS This is really a joke. Its not a database, not optimal in any way. But it works. .PP -The motd-of-lyskom text number is not saved anywhere. This makes the +The +.I message of the day +text number is not saved anywhere. This makes the server forget what text that is when restarting. +.SH NOTES +This will soon disapear and be replaced by something more bazaarly +inexplicable. diff --git a/doc/man/man5/lyskom.5 b/doc/man/man5/lyskom.5 index 1cb31d31e..e507faa7f 100644 --- a/doc/man/man5/lyskom.5 +++ b/doc/man/man5/lyskom.5 @@ -1,5 +1,5 @@ -.\" $Id: lyskom.5,v 1.2 1991/08/24 11:24:53 linus Exp $ -.\" $Date: 1991/08/24 11:24:53 $ +.\" $Id: lyskom.5,v 1.3 1991/08/24 11:51:46 linus Exp $ +.\" $Date: 1991/08/24 11:51:46 $ .TH ramkom 5 "August 24, 1991" .SH NAME ramkom - LysKOM @@ -9,9 +9,9 @@ format .B /usr/lyskom/db/ramkomd-* .br and -.PP -.B /usr/lyskom/etc/pid .br +.B /usr/lyskom/etc/pid +.PP .B #include <lyskom/kom-types.h> .SH DISCLAIMER The @@ -64,13 +64,13 @@ The different statuses types are and .B text .BR statuses . -I consider them as structs but in this file they are not saved as -structs but every element is save as a ascii string. Strings are -saved as holerith strings. The field of the struct is not even saved -in the same order as in the struct. The order they are saved in is -described below. +These are in a struct in the include file but in this file they are +not saved as structs but every element is saved as a ascii string. +Strings are saved as holerith strings. The field of the struct is not +even saved in the same order as in the struct. +Their order in the database is followed below. .PP -An array of things is reprecented in the database by a number telling +An array of things is represented in the database by a number telling how many elements there are in the array and the either a .B * in the case no elements or a @@ -82,7 +82,7 @@ followed by all the elements and a finishing This contains all information for a conference. A conference is a object that recieves texts. .TP 15 -.B Name +.I Name Name of the conference saved as a holerith string. .TP .I Member list @@ -126,7 +126,9 @@ box of the creator. .I Permitted submitters This is the number of the conference whose members are allowed to submit texts to this conference. If this is 0 (the default) all -persons i LysKOM are allowed to submit. +persons i +.B LysKOM +are allowed to submit. .TP .I Super conference This is a number of a conference that comments to articles should be @@ -174,7 +176,7 @@ element in the array is a text number and a mark number. .I Membership Here is the information about which conferences the person is member in. Its an array where every element is of the type -.I Membership +.B Membership (See below). .TP .I Last login @@ -185,7 +187,9 @@ Number of the text being the persons user area. If there is no user area this is 0. .TP .I Total time present -Time in LysKOM in seconds. +Time in +.B LysKOM +in seconds. .TP .I Sessions Number of logins made for that person. @@ -261,9 +265,30 @@ An array containing the texts that we have read after the .I Last text .IR read . This is necessary because its possible to read in any order. +.SH FILES +.TP 20 +.IB database-directory /db/ramkomd-data +File with all the elements and pointers. +.TP +.IB database-directory /db/ramkomd-texts +File with the texts. +.TP +.IB database-directory /etc/pid +File with the pid of the lyskom-process. +.TP +.IB database-directory /db/ramkomd-backup +Backup file with all data. +.SH "SEE ALSO" +.BR ramkomd (8), +.BR dbck (8) .SH BUGS This is really a joke. Its not a database, not optimal in any way. But it works. .PP -The motd-of-lyskom text number is not saved anywhere. This makes the +The +.I message of the day +text number is not saved anywhere. This makes the server forget what text that is when restarting. +.SH NOTES +This will soon disapear and be replaced by something more bazaarly +inexplicable. diff --git a/doc/man/man5/ramkom.5 b/doc/man/man5/ramkom.5 index f5da94d35..566375697 100644 --- a/doc/man/man5/ramkom.5 +++ b/doc/man/man5/ramkom.5 @@ -1,5 +1,5 @@ -.\" $Id: ramkom.5,v 1.2 1991/08/24 11:24:53 linus Exp $ -.\" $Date: 1991/08/24 11:24:53 $ +.\" $Id: ramkom.5,v 1.3 1991/08/24 11:51:46 linus Exp $ +.\" $Date: 1991/08/24 11:51:46 $ .TH ramkom 5 "August 24, 1991" .SH NAME ramkom - LysKOM @@ -9,9 +9,9 @@ format .B /usr/lyskom/db/ramkomd-* .br and -.PP -.B /usr/lyskom/etc/pid .br +.B /usr/lyskom/etc/pid +.PP .B #include <lyskom/kom-types.h> .SH DISCLAIMER The @@ -64,13 +64,13 @@ The different statuses types are and .B text .BR statuses . -I consider them as structs but in this file they are not saved as -structs but every element is save as a ascii string. Strings are -saved as holerith strings. The field of the struct is not even saved -in the same order as in the struct. The order they are saved in is -described below. +These are in a struct in the include file but in this file they are +not saved as structs but every element is saved as a ascii string. +Strings are saved as holerith strings. The field of the struct is not +even saved in the same order as in the struct. +Their order in the database is followed below. .PP -An array of things is reprecented in the database by a number telling +An array of things is represented in the database by a number telling how many elements there are in the array and the either a .B * in the case no elements or a @@ -82,7 +82,7 @@ followed by all the elements and a finishing This contains all information for a conference. A conference is a object that recieves texts. .TP 15 -.B Name +.I Name Name of the conference saved as a holerith string. .TP .I Member list @@ -126,7 +126,9 @@ box of the creator. .I Permitted submitters This is the number of the conference whose members are allowed to submit texts to this conference. If this is 0 (the default) all -persons i LysKOM are allowed to submit. +persons i +.B LysKOM +are allowed to submit. .TP .I Super conference This is a number of a conference that comments to articles should be @@ -174,7 +176,7 @@ element in the array is a text number and a mark number. .I Membership Here is the information about which conferences the person is member in. Its an array where every element is of the type -.I Membership +.B Membership (See below). .TP .I Last login @@ -185,7 +187,9 @@ Number of the text being the persons user area. If there is no user area this is 0. .TP .I Total time present -Time in LysKOM in seconds. +Time in +.B LysKOM +in seconds. .TP .I Sessions Number of logins made for that person. @@ -261,9 +265,30 @@ An array containing the texts that we have read after the .I Last text .IR read . This is necessary because its possible to read in any order. +.SH FILES +.TP 20 +.IB database-directory /db/ramkomd-data +File with all the elements and pointers. +.TP +.IB database-directory /db/ramkomd-texts +File with the texts. +.TP +.IB database-directory /etc/pid +File with the pid of the lyskom-process. +.TP +.IB database-directory /db/ramkomd-backup +Backup file with all data. +.SH "SEE ALSO" +.BR ramkomd (8), +.BR dbck (8) .SH BUGS This is really a joke. Its not a database, not optimal in any way. But it works. .PP -The motd-of-lyskom text number is not saved anywhere. This makes the +The +.I message of the day +text number is not saved anywhere. This makes the server forget what text that is when restarting. +.SH NOTES +This will soon disapear and be replaced by something more bazaarly +inexplicable. -- GitLab