diff --git a/doc/man/dbck.8 b/doc/man/dbck.8 index adf796e8e509ea04aac971b86d8cfba8a89dbba9..0027875e91da60f455bcfe1968479f50966b907b 100644 --- a/doc/man/dbck.8 +++ b/doc/man/dbck.8 @@ -1,5 +1,5 @@ -.\" $Id: dbck.8,v 1.3 1991/08/22 22:30:25 linus Exp $ -.\" $Date: 1991/08/22 22:30:25 $ +.\" $Id: dbck.8,v 1.4 1991/08/22 23:41:09 linus Exp $ +.\" $Date: 1991/08/22 23:41:09 $ .TH dbck 8 "August 22, 1991" .SH NAME dbck - reports and corrects errors in the LysKOM database. This @@ -25,7 +25,7 @@ all pointers are adjusted. This does only happen if the database was correct. .PP If none of the options -.B -r +.B -r, -i or .B -g are given the database is not changed. @@ -60,6 +60,19 @@ database. Do the garbage collect of the texts part of the database. This is sometimes called a compression of the text but it only removes non-referenced texts. +.SH NOTES +The messages +.I Conference <confno> has a bad Text-list. Starts with 0 +and +.I Person <persno> has created <number> conferences, not <number> (as +.I said in person-stat). +are normal. If you get them when you specify +.B -g, +let +.B dbck +fix them and run +.B dbck -g +again. .SH FILES .TP 20 .B /usr/lyskom @@ -72,12 +85,19 @@ File with all the elements and pointers. File with the texts. .TP .IB database-directory /db/ramkomd-backup -Backup file with all data. +Backup file of +.B ramkomd-data. .SH BUGS Does not lock the database. .PP Does never check if the database is locked. .PP Should have an unlock database option. +.PP +Does not check that +.B ramkomd-data +and +.B ramkomd-texts +are consistent. .SH AUTHOR Per Cederqvist <ceder@lysator.liu.se> diff --git a/doc/man/lyskomd.8 b/doc/man/lyskomd.8 index 83d1e34f216f8fb6ab9ffd93273dbdd35e4d34dd..b768dbf82eae2cdff64c3dbaf44931835203ebec 100644 --- a/doc/man/lyskomd.8 +++ b/doc/man/lyskomd.8 @@ -1,5 +1,5 @@ -.\" $Id: lyskomd.8,v 1.2 1991/08/22 22:30:29 linus Exp $ -.\" $Date: 1991/08/22 22:30:29 $ +.\" $Id: lyskomd.8,v 1.3 1991/08/22 23:41:12 linus Exp $ +.\" $Date: 1991/08/22 23:41:12 $ .TH ramkomd 8 "August 22, 1991" .SH NAME ramkomd - LysKOM server @@ -25,14 +25,13 @@ It listens for connections on the given portnumbers (defaults are 4894 for the .I clientportnumber and 4787 for the -.I muxportnumber -). +.IR muxportnumber ). .SH OPTIONS .TP .B \-d Adds one to the debug-level i.e. increases the amount of output on the stderr from the process. -.TP + Using one .B \-d make the process print a @@ -44,18 +43,14 @@ communication to the process. .B \-q Never save the database. .TP -.BI -D database-directory +.BI \-D database-directory Use the database in the .I database-directory. .br Example: If your database is in -.ft B -$HOME/lyskom/db -.ft R +.B $HOME/lyskom/db you should use the option -.ft B --D$HOME/lyskom -.ft R +.B \-D$HOME/lyskom .TP .BI \-p clientportnumber listens for clients on the port number @@ -87,6 +82,14 @@ File with the pid of the lyskom-process. .IB database-directory /db/ramkomd-backup Backup file with all data. .SH BUGS -Yes. +Small memory leak. +.PP +There is no practical handling of security. +.PP +The choice of asynchronously issued messages is not very good. +.PP +The so called "data base" is a joke. .SH AUTHOR Per Cederqvist <ceder@lysator.liu.se> +.SH NOTE +Version 2.0 on its way. diff --git a/doc/man/man8/dbck.8 b/doc/man/man8/dbck.8 index adf796e8e509ea04aac971b86d8cfba8a89dbba9..0027875e91da60f455bcfe1968479f50966b907b 100644 --- a/doc/man/man8/dbck.8 +++ b/doc/man/man8/dbck.8 @@ -1,5 +1,5 @@ -.\" $Id: dbck.8,v 1.3 1991/08/22 22:30:25 linus Exp $ -.\" $Date: 1991/08/22 22:30:25 $ +.\" $Id: dbck.8,v 1.4 1991/08/22 23:41:09 linus Exp $ +.\" $Date: 1991/08/22 23:41:09 $ .TH dbck 8 "August 22, 1991" .SH NAME dbck - reports and corrects errors in the LysKOM database. This @@ -25,7 +25,7 @@ all pointers are adjusted. This does only happen if the database was correct. .PP If none of the options -.B -r +.B -r, -i or .B -g are given the database is not changed. @@ -60,6 +60,19 @@ database. Do the garbage collect of the texts part of the database. This is sometimes called a compression of the text but it only removes non-referenced texts. +.SH NOTES +The messages +.I Conference <confno> has a bad Text-list. Starts with 0 +and +.I Person <persno> has created <number> conferences, not <number> (as +.I said in person-stat). +are normal. If you get them when you specify +.B -g, +let +.B dbck +fix them and run +.B dbck -g +again. .SH FILES .TP 20 .B /usr/lyskom @@ -72,12 +85,19 @@ File with all the elements and pointers. File with the texts. .TP .IB database-directory /db/ramkomd-backup -Backup file with all data. +Backup file of +.B ramkomd-data. .SH BUGS Does not lock the database. .PP Does never check if the database is locked. .PP Should have an unlock database option. +.PP +Does not check that +.B ramkomd-data +and +.B ramkomd-texts +are consistent. .SH AUTHOR Per Cederqvist <ceder@lysator.liu.se> diff --git a/doc/man/man8/lyskomd.8 b/doc/man/man8/lyskomd.8 index 83d1e34f216f8fb6ab9ffd93273dbdd35e4d34dd..b768dbf82eae2cdff64c3dbaf44931835203ebec 100644 --- a/doc/man/man8/lyskomd.8 +++ b/doc/man/man8/lyskomd.8 @@ -1,5 +1,5 @@ -.\" $Id: lyskomd.8,v 1.2 1991/08/22 22:30:29 linus Exp $ -.\" $Date: 1991/08/22 22:30:29 $ +.\" $Id: lyskomd.8,v 1.3 1991/08/22 23:41:12 linus Exp $ +.\" $Date: 1991/08/22 23:41:12 $ .TH ramkomd 8 "August 22, 1991" .SH NAME ramkomd - LysKOM server @@ -25,14 +25,13 @@ It listens for connections on the given portnumbers (defaults are 4894 for the .I clientportnumber and 4787 for the -.I muxportnumber -). +.IR muxportnumber ). .SH OPTIONS .TP .B \-d Adds one to the debug-level i.e. increases the amount of output on the stderr from the process. -.TP + Using one .B \-d make the process print a @@ -44,18 +43,14 @@ communication to the process. .B \-q Never save the database. .TP -.BI -D database-directory +.BI \-D database-directory Use the database in the .I database-directory. .br Example: If your database is in -.ft B -$HOME/lyskom/db -.ft R +.B $HOME/lyskom/db you should use the option -.ft B --D$HOME/lyskom -.ft R +.B \-D$HOME/lyskom .TP .BI \-p clientportnumber listens for clients on the port number @@ -87,6 +82,14 @@ File with the pid of the lyskom-process. .IB database-directory /db/ramkomd-backup Backup file with all data. .SH BUGS -Yes. +Small memory leak. +.PP +There is no practical handling of security. +.PP +The choice of asynchronously issued messages is not very good. +.PP +The so called "data base" is a joke. .SH AUTHOR Per Cederqvist <ceder@lysator.liu.se> +.SH NOTE +Version 2.0 on its way. diff --git a/doc/man/man8/ramkomd.8 b/doc/man/man8/ramkomd.8 index 9ca19c9c0a5502003a6ecc0425cdfc2f572749ac..35143d519d215bfe2a15b27320612080f6d884a9 100644 --- a/doc/man/man8/ramkomd.8 +++ b/doc/man/man8/ramkomd.8 @@ -1,5 +1,5 @@ -.\" $Id: ramkomd.8,v 1.2 1991/08/22 22:30:29 linus Exp $ -.\" $Date: 1991/08/22 22:30:29 $ +.\" $Id: ramkomd.8,v 1.3 1991/08/22 23:41:12 linus Exp $ +.\" $Date: 1991/08/22 23:41:12 $ .TH ramkomd 8 "August 22, 1991" .SH NAME ramkomd - LysKOM server @@ -25,14 +25,13 @@ It listens for connections on the given portnumbers (defaults are 4894 for the .I clientportnumber and 4787 for the -.I muxportnumber -). +.IR muxportnumber ). .SH OPTIONS .TP .B \-d Adds one to the debug-level i.e. increases the amount of output on the stderr from the process. -.TP + Using one .B \-d make the process print a @@ -44,18 +43,14 @@ communication to the process. .B \-q Never save the database. .TP -.BI -D database-directory +.BI \-D database-directory Use the database in the .I database-directory. .br Example: If your database is in -.ft B -$HOME/lyskom/db -.ft R +.B $HOME/lyskom/db you should use the option -.ft B --D$HOME/lyskom -.ft R +.B \-D$HOME/lyskom .TP .BI \-p clientportnumber listens for clients on the port number @@ -87,6 +82,14 @@ File with the pid of the lyskom-process. .IB database-directory /db/ramkomd-backup Backup file with all data. .SH BUGS -Yes. +Small memory leak. +.PP +There is no practical handling of security. +.PP +The choice of asynchronously issued messages is not very good. +.PP +The so called "data base" is a joke. .SH AUTHOR Per Cederqvist <ceder@lysator.liu.se> +.SH NOTE +Version 2.0 on its way.