serveral updates for running DOS doors
This commit is contained in:
Michiel Broek
@@ -1,117 +1,117 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" "content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>BBS doors dropfiles.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 02-Feb-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1>BBS doors dropfiles.</H1>
|
||||
<P>
|
||||
|
||||
<h3>Dropfiles for Unix BBS systems.</h3>
|
||||
<p>
|
||||
Not all options that are available under DOS or OS/2 can be used with Unix
|
||||
BBS systems and must be faked.
|
||||
<p> <P>
|
||||
|
||||
<h3>DOOR.SYS format.</h3>
|
||||
<P>
|
||||
The door.sys format is a 52 lines ascii textfile, each line is terminated with
|
||||
a cr/lf pair. In the setup it is possible to force the creation of MM-DD-YYYY
|
||||
dates instead of the MM-DD-YY style. Newer doors sometimes need that.
|
||||
<pre>
|
||||
Line Description
|
||||
----- -----------------------------------------------------------------
|
||||
1 Port, 2 characters in DOS format, p.e. COM1
|
||||
2 Effective Baudrate
|
||||
3 Databits
|
||||
4 Nodenumber, 1..9999
|
||||
5 Locked baudrate
|
||||
6 Screen display, Y=snoop on, N=snoop off. On Linux allways N.
|
||||
7 Printer Y=on N=off
|
||||
8 Page Bell Y=on N=off
|
||||
9 Caller alarm Y=on N=off
|
||||
10 Users first name and lastname
|
||||
11 Users location
|
||||
12 Voice/Home phone
|
||||
13 Work/Dataphone
|
||||
14 Password, empty if not available (stored coded).
|
||||
15 Security level, 0..32768
|
||||
16 Users number of calls
|
||||
17 Users last call date MM-DD-YY
|
||||
18 Seconds remaining this call
|
||||
19 Time left in minutes
|
||||
20 ANSI, "GR" is yes, otherwise ?
|
||||
21 Screen length
|
||||
22 User mode, always N
|
||||
23 Always blank
|
||||
24 Always blank
|
||||
25 Subscription expire date MM-DD-YY
|
||||
26 Users record number
|
||||
27 Default protocol
|
||||
28 Users total number of uploads
|
||||
29 Users total number of downloads
|
||||
30 Users daily download kilobytes total
|
||||
31 Daily download kilobyte limit
|
||||
32 Users date of birth MM-DD-YY
|
||||
33 Path to users database files Cannot be used on Linux.
|
||||
34 Path to message database files
|
||||
35 Sysop first and last name
|
||||
36 Users handle
|
||||
37 Next event starting time or "none"
|
||||
38 Error-free connection Y=Yes or N=No
|
||||
39 Always set to N
|
||||
40 Always set to Y
|
||||
41 Text color as defined in setup 7 = gray.
|
||||
42 Always 0
|
||||
43 Last new files scan date MM-DD-YY
|
||||
44 Time of this call HH:MM
|
||||
45 Time of last call HH:MM
|
||||
46 Always set to 32768
|
||||
47 Number of files downloaded today
|
||||
48 Total kilobytes uploaded
|
||||
49 Total kilobytes downloaded
|
||||
50 Comment stored in users record
|
||||
51 Always set to 0
|
||||
52 Total number of messages posted
|
||||
</pre>
|
||||
<P> <P>
|
||||
|
||||
<h3>DORINFOn.DEF dropfile.</H3>
|
||||
<P>
|
||||
The DORINFOn.DEF file is a 12 lines ascii textfile, each line terminated with
|
||||
a cr/lf pair. All characters in the file are uppercase. The n in the filename
|
||||
represents the current line number and will be between 1 and 9. Using number
|
||||
1 seems always fine.
|
||||
<pre>
|
||||
Line Description
|
||||
------ ------------------------------------------------------------------
|
||||
1 System name
|
||||
2 Sysop's first name
|
||||
3 Sysop's last name
|
||||
4 Port name, like COM1, COM2 etc. COM0 = local
|
||||
5 Baudrate format: "19200 BAUD-R,N,8,1"
|
||||
6 Always 0
|
||||
7 Users firstname
|
||||
8 Users lastname
|
||||
9 Users location
|
||||
10 Graphics mode: 0=no, 1=ANSI, 2=Avatar, 3=ANSI+Avatar
|
||||
11 Security level, 0..32767
|
||||
12 Time left in minutes
|
||||
</pre>
|
||||
<p>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>BBS doors dropfiles.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 22-Oct-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1>BBS doors dropfiles.</H1>
|
||||
<P>
|
||||
|
||||
<h3>Dropfiles for Unix BBS systems.</h3>
|
||||
<p>
|
||||
Not all options that are available under DOS or OS/2 can be used with Unix
|
||||
BBS systems and must be faked.
|
||||
<p> <P>
|
||||
|
||||
<h3>DOOR.SYS format.</h3>
|
||||
<P>
|
||||
The door.sys format is a 52 lines ascii textfile, each line is terminated with
|
||||
a cr/lf pair. In the setup it is possible to force the creation of MM-DD-YYYY
|
||||
dates instead of the MM-DD-YY style. Newer doors sometimes need that.
|
||||
<pre>
|
||||
Line Description
|
||||
----- -----------------------------------------------------------------
|
||||
1 Port, 5 characters in DOS format, p.e. COM1:
|
||||
2 Effective Baudrate
|
||||
3 Databits
|
||||
4 Nodenumber, 1..9999
|
||||
5 Locked baudrate
|
||||
6 Screen display, Y=snoop on, N=snoop off. On Linux allways N.
|
||||
7 Printer Y=on N=off
|
||||
8 Page Bell Y=on N=off
|
||||
9 Caller alarm Y=on N=off
|
||||
10 Users first name and lastname
|
||||
11 Users location
|
||||
12 Voice/Home phone
|
||||
13 Work/Dataphone
|
||||
14 Password, empty if not available (stored coded).
|
||||
15 Security level, 0..32768
|
||||
16 Users number of calls
|
||||
17 Users last call date MM-DD-YY
|
||||
18 Seconds remaining this call
|
||||
19 Time left in minutes
|
||||
20 ANSI, "GR" is yes, otherwise ?
|
||||
21 Screen length
|
||||
22 User mode, always N
|
||||
23 Always blank
|
||||
24 Always blank
|
||||
25 Subscription expire date MM-DD-YY
|
||||
26 Users record number
|
||||
27 Default protocol
|
||||
28 Users total number of uploads
|
||||
29 Users total number of downloads
|
||||
30 Users daily download kilobytes total
|
||||
31 Daily download kilobyte limit
|
||||
32 Users date of birth MM-DD-YY
|
||||
33 Path to users database files Cannot be used on Linux.
|
||||
34 Path to message database files
|
||||
35 Sysop first and last name
|
||||
36 Users handle
|
||||
37 Next event starting time or "none"
|
||||
38 Error-free connection Y=Yes or N=No
|
||||
39 Always set to N
|
||||
40 Always set to Y
|
||||
41 Text color as defined in setup 7 = gray.
|
||||
42 Always 0
|
||||
43 Last new files scan date MM-DD-YY
|
||||
44 Time of this call HH:MM
|
||||
45 Time of last call HH:MM
|
||||
46 Always set to 32768
|
||||
47 Number of files downloaded today
|
||||
48 Total kilobytes uploaded
|
||||
49 Total kilobytes downloaded
|
||||
50 Comment stored in users record
|
||||
51 Always set to 0
|
||||
52 Total number of messages posted
|
||||
</pre>
|
||||
<P> <P>
|
||||
|
||||
<h3>DORINFOn.DEF dropfile.</H3>
|
||||
<P>
|
||||
The DORINFOn.DEF file is a 12 lines ascii textfile, each line terminated with
|
||||
a cr/lf pair. All characters in the file are uppercase. The n in the filename
|
||||
represents the current line number and will be between 1 and 9. Using number
|
||||
1 seems always fine.
|
||||
<pre>
|
||||
Line Description
|
||||
------ ------------------------------------------------------------------
|
||||
1 System name
|
||||
2 Sysop's first name
|
||||
3 Sysop's last name
|
||||
4 Port name, like COM1, COM2 etc. COM0 = local
|
||||
5 Baudrate format: "19200 BAUD-R,N,8,1"
|
||||
6 Always 0
|
||||
7 Users firstname
|
||||
8 Users lastname
|
||||
9 Users location
|
||||
10 Graphics mode: 0=no, 1=ANSI, 2=Avatar, 3=ANSI+Avatar
|
||||
11 Security level, 0..32767
|
||||
12 Time left in minutes
|
||||
</pre>
|
||||
<p>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
@@ -1,98 +1,98 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" "content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Howto setup an FTP server to work with MBSE BBS.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 06-Jun-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1>How to setup an FTP server to work with MBSE BBS.</H1>
|
||||
<P>
|
||||
|
||||
In order to let MBSE BBS and your FTP server to both function together you must
|
||||
organize a special file structure. Note that even if you don't setup an FTP
|
||||
server you must still create a structure like this for the fidonet mailer,
|
||||
if you don't, <strong>mail and files will get lost!</strong>
|
||||
Note that this description is written for wu-ftpd, on your distribution there
|
||||
may be another ftpd installed. <font color=red><u>Don't use mbftpd yet!</u></font>
|
||||
<P>
|
||||
<H4>The filestructure I used is as follows:</H4>
|
||||
<PRE>
|
||||
/var/spool/mbse/ftp/pub/dos_util/dos_4dos - Public download areas
|
||||
| | | /dos_disk
|
||||
| | | /dos_file
|
||||
| | /virnet/mcafee
|
||||
| | /win16
|
||||
| | /win32
|
||||
| /bin - FTP bin directory
|
||||
| /etc - FTP etc directory
|
||||
| /incoming - FTP public upload.
|
||||
/mail/out - Your default outbound
|
||||
| /out.009 - Outbound Zone 9
|
||||
| /inbound - Inbound directory
|
||||
/raonly/upload - Non-public download areas
|
||||
| /sysop
|
||||
| /logfiles
|
||||
/tic_queue - Queue for .tic files.
|
||||
|
||||
</PRE>
|
||||
|
||||
In order to give DOS style names for fidonet sessions you must set the
|
||||
DOS path and Unix path in <strong>mbsetup</strong> (1.3.11 and 1.3.12) to
|
||||
<strong>"m:"</strong> and <strong>"/var/spool/mbse"</strong>. Note that to get
|
||||
forwarding of .tic files to work the <strong>tic_queue</strong> must be a
|
||||
subdirectory of "/var/spool/mbse" too. You could actually use any drive letter for
|
||||
the DOS path.
|
||||
<P>
|
||||
This means that a fidonet file attach from the dos_4dos public download
|
||||
directory shall get the subject "M:\FTP\PUB\DOS_UTIL\DOS_4DOS\COMMAND.ZIP".
|
||||
|
||||
<P>
|
||||
As you can see, anonymous ftp users can't get to the mail, non-public
|
||||
downloads etc. Normally, your BBS users have unix accounts and will be able
|
||||
to do a ftp login and access any directory on your system. Because the bbs
|
||||
users have <b>mbsebbs</b> as their shell and this shell is not in the file
|
||||
<b>/etc/shells</b> the ftp daemon will not let the bbs users in. So even
|
||||
your own bbs users must login as anonymous to get files from the ftp server.
|
||||
<P>
|
||||
Note the following directory permissions MUST BE SET!!!!::: See also
|
||||
the man pages for the DARPA ftpd server.
|
||||
<P>
|
||||
|
||||
<PRE>
|
||||
Directory owner group mode perms
|
||||
------------------------------- ----- ----- ---- ----------
|
||||
/var/spool/mbse mbse bbs 0755 drwxr-xr-x
|
||||
/var/spool/mbse/ftp root wheel 0555 dr-xr-xr-x
|
||||
/var/spool/mbse/ftp/bin root wheel 0555 dr-xr-xr-x
|
||||
/var/spool/mbse/ftp/bin/ls root bin 0111 ---x--x--x
|
||||
/var/spool/mbse/ftp/etc root root 0555 dr-xr-xr-x
|
||||
/var/spool/mbse/ftp/etc/passwd root root 0444 -r--r--r--
|
||||
/var/spool/mbse/ftp/etc/group root root 0444 -r--r--r--
|
||||
/var/spool/mbse/ftp/pub mbse bbs 0775 drwxrwxr-x
|
||||
/var/spool/mbse/ftp/incoming ftp users 0755 drwxr-xr-x
|
||||
|
||||
</PRE>
|
||||
Note that all subdirectories under ../pub also must be owned by <strong>mbse
|
||||
</strong> and group <strong>bbs</strong> and have at least mode 775 as long
|
||||
as it are real bbs subdirectories. The bbs will maintain these directories
|
||||
automatic and must have the rights to do so.
|
||||
|
||||
<P>
|
||||
In the /var/spool/mbse/ftp/etc/group file, add the group bbs so that your directory
|
||||
listings give the proper groupname instead of a number.
|
||||
<P>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Howto setup an FTP server to work with MBSE BBS.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 06-Jun-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1>How to setup an FTP server to work with MBSE BBS.</H1>
|
||||
<P>
|
||||
|
||||
In order to let MBSE BBS and your FTP server to both function together you must
|
||||
organize a special file structure. Note that even if you don't setup an FTP
|
||||
server you must still create a structure like this for the fidonet mailer,
|
||||
if you don't, <strong>mail and files will get lost!</strong>
|
||||
Note that this description is written for wu-ftpd, on your distribution there
|
||||
may be another ftpd installed. <font color=red><u>Don't use mbftpd yet!</u></font>
|
||||
<P>
|
||||
<H4>The filestructure I used is as follows:</H4>
|
||||
<PRE>
|
||||
/var/spool/mbse/ftp/pub/dos_util/dos_4dos - Public download areas
|
||||
| | | /dos_disk
|
||||
| | | /dos_file
|
||||
| | /virnet/mcafee
|
||||
| | /win16
|
||||
| | /win32
|
||||
| /bin - FTP bin directory
|
||||
| /etc - FTP etc directory
|
||||
| /incoming - FTP public upload.
|
||||
/mail/out - Your default outbound
|
||||
| /out.009 - Outbound Zone 9
|
||||
| /inbound - Inbound directory
|
||||
/raonly/upload - Non-public download areas
|
||||
| /sysop
|
||||
| /logfiles
|
||||
/tic_queue - Queue for .tic files.
|
||||
|
||||
</PRE>
|
||||
|
||||
In order to give DOS style names for fidonet sessions you must set the
|
||||
DOS path and Unix path in <strong>mbsetup</strong> (1.3.11 and 1.3.12) to
|
||||
<strong>"m:"</strong> and <strong>"/var/spool/mbse"</strong>. Note that to get
|
||||
forwarding of .tic files to work the <strong>tic_queue</strong> must be a
|
||||
subdirectory of "/var/spool/mbse" too. You could actually use any drive letter for
|
||||
the DOS path.
|
||||
<P>
|
||||
This means that a fidonet file attach from the dos_4dos public download
|
||||
directory shall get the subject "M:\FTP\PUB\DOS_UTIL\DOS_4DOS\COMMAND.ZIP".
|
||||
|
||||
<P>
|
||||
As you can see, anonymous ftp users can't get to the mail, non-public
|
||||
downloads etc. Normally, your BBS users have unix accounts and will be able
|
||||
to do a ftp login and access any directory on your system. Because the bbs
|
||||
users have <b>mbsebbs</b> as their shell and this shell is not in the file
|
||||
<b>/etc/shells</b> the ftp daemon will not let the bbs users in. So even
|
||||
your own bbs users must login as anonymous to get files from the ftp server.
|
||||
<P>
|
||||
Note the following directory permissions MUST BE SET!!!!::: See also
|
||||
the man pages for the DARPA ftpd server.
|
||||
<P>
|
||||
|
||||
<PRE>
|
||||
Directory owner group mode perms
|
||||
------------------------------- ----- ----- ---- ----------
|
||||
/var/spool/mbse mbse bbs 0755 drwxr-xr-x
|
||||
/var/spool/mbse/ftp root wheel 0555 dr-xr-xr-x
|
||||
/var/spool/mbse/ftp/bin root wheel 0555 dr-xr-xr-x
|
||||
/var/spool/mbse/ftp/bin/ls root bin 0111 ---x--x--x
|
||||
/var/spool/mbse/ftp/etc root root 0555 dr-xr-xr-x
|
||||
/var/spool/mbse/ftp/etc/passwd root root 0444 -r--r--r--
|
||||
/var/spool/mbse/ftp/etc/group root root 0444 -r--r--r--
|
||||
/var/spool/mbse/ftp/pub mbse bbs 0775 drwxrwxr-x
|
||||
/var/spool/mbse/ftp/incoming ftp users 0755 drwxr-xr-x
|
||||
|
||||
</PRE>
|
||||
Note that all subdirectories under ../pub also must be owned by <strong>mbse
|
||||
</strong> and group <strong>bbs</strong> and have at least mode 775 as long
|
||||
as it are real bbs subdirectories. The bbs will maintain these directories
|
||||
automatic and must have the rights to do so.
|
||||
|
||||
<P>
|
||||
In the /var/spool/mbse/ftp/etc/group file, add the group bbs so that your directory
|
||||
listings give the proper groupname instead of a number.
|
||||
<P>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
@@ -1,46 +1,46 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" "content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Miscellaneous Documents</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 02-Feb-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<h1>Miscellaneous Documents</h1>
|
||||
|
||||
<h3>Introduction</h3>
|
||||
<P>
|
||||
This is an overview of used unofficial documents for the development of the
|
||||
MBSE BBS package.
|
||||
<P>
|
||||
Michiel Broek.
|
||||
<P>
|
||||
<hr>
|
||||
<h3>Documents</h3>
|
||||
<ul>
|
||||
<li><a href="filefind.html">Implementation and Usage of Filefind Utilities, R.Williamson</a>
|
||||
<li><a href="ipmailer.html">Integration of IP-Nodes in the nodelist, L.Behet</a>
|
||||
<li><a href="fileid.html">FILE_ID.DIZ Information, R.Moller</a>
|
||||
<li><a href="ftpserver.html">How to setup an FTP server with MBSE BBS, M.Broek</a>
|
||||
<li><a href="jam.html">JAM Message Base Proposal, J.Homrighausen</a>
|
||||
<li><a href="outbound.html">Binkley style mailer outbound for MBSE BBS, M.Broek</a>
|
||||
<li><a href="semafore.html">Semafore files for MBSE BBS, M.Broek</a>
|
||||
<li><a href="usleep.html">System load and usleep() code, M.Broek</a>
|
||||
<li><a href="dropfile.html">BBS doors dropfiles, M. Broek</a>
|
||||
</ul>
|
||||
|
||||
<HR>
|
||||
|
||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Miscellaneous Documents</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 02-Feb-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<h1>Miscellaneous Documents</h1>
|
||||
|
||||
<h3>Introduction</h3>
|
||||
<P>
|
||||
This is an overview of used unofficial documents for the development of the
|
||||
MBSE BBS package.
|
||||
<P>
|
||||
Michiel Broek.
|
||||
<P>
|
||||
<hr>
|
||||
<h3>Documents</h3>
|
||||
<ul>
|
||||
<li><a href="filefind.html">Implementation and Usage of Filefind Utilities, R.Williamson</a>
|
||||
<li><a href="ipmailer.html">Integration of IP-Nodes in the nodelist, L.Behet</a>
|
||||
<li><a href="fileid.html">FILE_ID.DIZ Information, R.Moller</a>
|
||||
<li><a href="ftpserver.html">How to setup an FTP server with MBSE BBS, M.Broek</a>
|
||||
<li><a href="jam.html">JAM Message Base Proposal, J.Homrighausen</a>
|
||||
<li><a href="outbound.html">Binkley style mailer outbound for MBSE BBS, M.Broek</a>
|
||||
<li><a href="semafore.html">Semafore files for MBSE BBS, M.Broek</a>
|
||||
<li><a href="usleep.html">System load and usleep() code, M.Broek</a>
|
||||
<li><a href="dropfile.html">BBS doors dropfiles, M. Broek</a>
|
||||
</ul>
|
||||
|
||||
<HR>
|
||||
|
||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
@@ -1,172 +1,172 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Integration of IP-Nodes in the nodelist.</TITLE>
|
||||
</HEAD>
|
||||
|
||||
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
||||
<BODY
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#000080"
|
||||
ALINK="#FF0000"
|
||||
>
|
||||
<PRE>
|
||||
Publication: FSP-????
|
||||
Revision: 1
|
||||
Title: Integration of IP-Nodes in the nodelist (FTS-0005)
|
||||
Author: Lothar Behet, 2:2446/301
|
||||
Revision Date: 25 October 1998
|
||||
Expiry Date:
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Contents:
|
||||
1. Required fields according to FTS-0005, basic flags for ip-nodes
|
||||
2. Optional extensions
|
||||
3. Addendum
|
||||
----------------------------------------------------------------------
|
||||
|
||||
1. Description of the nodelist format
|
||||
--------------------------------------
|
||||
|
||||
Every node entry contains the following 8 fields:
|
||||
|
||||
keyword,node_number,node_name,location,sysop_name,
|
||||
phone_number,baud_rate,flags
|
||||
|
||||
Certain fields have defined values according to FTS-0005.
|
||||
|
||||
1.1. Implementation for IP-connectivity
|
||||
Because of the limited characterset in the phone_field and
|
||||
to avoid any misinterpretion by conventional dialing, the
|
||||
ip-specific address-information is entered in another field
|
||||
and there are additional flags required.
|
||||
|
||||
1.1.1. Field #1 (keyword) is PVT for an ip-only node without
|
||||
conventional phone number related connectivity. In this
|
||||
case, the phone field contains "-Unpublished-" according
|
||||
to FTS-0005.
|
||||
|
||||
1.1.2. Field #2 (node_number) contains the node number within his
|
||||
net and zone.
|
||||
|
||||
1.1.3. Field #3 (node_name) is used for the FQDN (Fully Qualified
|
||||
Domain Name) or the ip-address.
|
||||
|
||||
1.1.4. Field #4 (location) contains the geographical location of
|
||||
the node. While some nets/regions cannot supply their
|
||||
ip-only nodes with a adequate link, these nodes may be
|
||||
collected in a seperate net or region, until their original
|
||||
net/region support additional ip-connectivity. This special
|
||||
net/region is definitely a temporary solution for routing
|
||||
within a region or zone!
|
||||
|
||||
1.1.5. Field #5 (sysop_name) represants the name of the system
|
||||
operator.
|
||||
|
||||
1.1.6. Field #6 (phone_number) contains the phone_number for
|
||||
conventional connectivity. In case of an ip-only node
|
||||
it must contain "-Unpublished-".
|
||||
|
||||
1.1.7. Field #7 (baud_rate) contains the maximum baud rate for
|
||||
conventional connectivity or 300 in case of an ip_only node.
|
||||
|
||||
1.1.8. Field #8 (flags) represents operational definitions for the
|
||||
node.
|
||||
Note that these are user flags.
|
||||
The ip-flags consist of two parts:
|
||||
A basic transport and an optional non-standard port,
|
||||
seperated by a colon.
|
||||
The default port may be omitted, but is listed as optional
|
||||
parameter in this document. In some cases, two flag names
|
||||
are mentioned:
|
||||
The second one is supported by some software nowadays, but
|
||||
these values may conflict with other programs, which not
|
||||
completely decode the length of each individual flag (i.e.
|
||||
TELN conflicts with the T-flag for online-time)
|
||||
Additional flags for ip-nodes are:
|
||||
|
||||
1.1.8.1. IBN[:24554] (Argus: BND[:24554])
|
||||
BinkP protocol
|
||||
|
||||
1.1.8.2. IFC[:60179]
|
||||
Raw protocol as used by ifcico
|
||||
|
||||
1.1.8.3. ITN[:23] (Argus: TEL[:23])
|
||||
Telnet protocol. Some variants of ifcico support Telnet
|
||||
on port 60177, which should be added as additional flag
|
||||
ITN:60177.
|
||||
|
||||
1.1.8.4. IVM[:3141]
|
||||
Vmodem protocol
|
||||
|
||||
1.1.8.5. IP
|
||||
General flag for special protocol specifications, if the
|
||||
flags conforming to 1.1.8.1. to 1.1.8.4. are not relevant.
|
||||
|
||||
1.1.9. Comments on the proposed nodelist flags
|
||||
The additional flagnames in () are supported at this moment
|
||||
by Argus, based on the use in z2r50. But the TEL[NET]-flag
|
||||
stays in conflict with the generally in all zones and
|
||||
regions used T-flag (online time according to FSC-0062).
|
||||
|
||||
|
||||
2. Optional extensions for future use
|
||||
--------------------------------------
|
||||
|
||||
While the above mentioned flags (1.1.8.1 to 1.1.8.4) define a
|
||||
minimum set of operational flags for ip-nodes, several additions
|
||||
are already foreseeable at this moment.
|
||||
|
||||
2.1. Additional sessions_handshake parameters
|
||||
There is at least one program, which supports several
|
||||
transport protocols according to chapter 1.1.8. on a
|
||||
single port. If other programs should imitate this habit,
|
||||
then the following extension to the flag suite 1.1.8.
|
||||
(transport[:port[:handshake]])is advised:
|
||||
|
||||
2.1.1. FTS-0001 session handshake: 1
|
||||
2.1.2. Yoohoo session handshake : Y
|
||||
2.1.3. EMSI sessions handshake : E
|
||||
2.1.4. BinkP sessions handshake : B
|
||||
|
||||
2.2. Non-handshaking protocols
|
||||
While the definitions until this chapter describe direct
|
||||
handshaking sessions with optional password authentification,
|
||||
there are several other methods for the tunneling of fidonet
|
||||
data via the internet available.
|
||||
The setup of these connections does not rely on the nodelist
|
||||
(at this moment of writing), but we can think of standard
|
||||
setup procedures to use the nodelist for configuration of
|
||||
this additional transport methods.
|
||||
Therefore the following flags 2.2.1. to 2.2.4. are advised
|
||||
for at least informational purpose.
|
||||
|
||||
2.2.1. IFT
|
||||
FTP (File Transfer Protocol)
|
||||
|
||||
2.2.2. ITX
|
||||
TransX, an Email based variant
|
||||
|
||||
2.2.3. IUC
|
||||
Uuencoded packet (one packet per message)
|
||||
|
||||
2.2.4. IEM
|
||||
Email based (generally, without exact specification at
|
||||
this moment)
|
||||
|
||||
|
||||
3. Addendum
|
||||
------------
|
||||
|
||||
This proposal is based on a maximum compatibility to generally used
|
||||
definitions and standards within the Fidonet community.
|
||||
Future developments might make additions necessary, if they can not
|
||||
be expressed with the existing set of flags as defined by this FSP.
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Integration of IP-Nodes in the nodelist.</TITLE>
|
||||
</HEAD>
|
||||
|
||||
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
||||
<BODY
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#000080"
|
||||
ALINK="#FF0000"
|
||||
>
|
||||
<PRE>
|
||||
Publication: FSP-????
|
||||
Revision: 1
|
||||
Title: Integration of IP-Nodes in the nodelist (FTS-0005)
|
||||
Author: Lothar Behet, 2:2446/301
|
||||
Revision Date: 25 October 1998
|
||||
Expiry Date:
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Contents:
|
||||
1. Required fields according to FTS-0005, basic flags for ip-nodes
|
||||
2. Optional extensions
|
||||
3. Addendum
|
||||
----------------------------------------------------------------------
|
||||
|
||||
1. Description of the nodelist format
|
||||
--------------------------------------
|
||||
|
||||
Every node entry contains the following 8 fields:
|
||||
|
||||
keyword,node_number,node_name,location,sysop_name,
|
||||
phone_number,baud_rate,flags
|
||||
|
||||
Certain fields have defined values according to FTS-0005.
|
||||
|
||||
1.1. Implementation for IP-connectivity
|
||||
Because of the limited characterset in the phone_field and
|
||||
to avoid any misinterpretion by conventional dialing, the
|
||||
ip-specific address-information is entered in another field
|
||||
and there are additional flags required.
|
||||
|
||||
1.1.1. Field #1 (keyword) is PVT for an ip-only node without
|
||||
conventional phone number related connectivity. In this
|
||||
case, the phone field contains "-Unpublished-" according
|
||||
to FTS-0005.
|
||||
|
||||
1.1.2. Field #2 (node_number) contains the node number within his
|
||||
net and zone.
|
||||
|
||||
1.1.3. Field #3 (node_name) is used for the FQDN (Fully Qualified
|
||||
Domain Name) or the ip-address.
|
||||
|
||||
1.1.4. Field #4 (location) contains the geographical location of
|
||||
the node. While some nets/regions cannot supply their
|
||||
ip-only nodes with a adequate link, these nodes may be
|
||||
collected in a seperate net or region, until their original
|
||||
net/region support additional ip-connectivity. This special
|
||||
net/region is definitely a temporary solution for routing
|
||||
within a region or zone!
|
||||
|
||||
1.1.5. Field #5 (sysop_name) represants the name of the system
|
||||
operator.
|
||||
|
||||
1.1.6. Field #6 (phone_number) contains the phone_number for
|
||||
conventional connectivity. In case of an ip-only node
|
||||
it must contain "-Unpublished-".
|
||||
|
||||
1.1.7. Field #7 (baud_rate) contains the maximum baud rate for
|
||||
conventional connectivity or 300 in case of an ip_only node.
|
||||
|
||||
1.1.8. Field #8 (flags) represents operational definitions for the
|
||||
node.
|
||||
Note that these are user flags.
|
||||
The ip-flags consist of two parts:
|
||||
A basic transport and an optional non-standard port,
|
||||
seperated by a colon.
|
||||
The default port may be omitted, but is listed as optional
|
||||
parameter in this document. In some cases, two flag names
|
||||
are mentioned:
|
||||
The second one is supported by some software nowadays, but
|
||||
these values may conflict with other programs, which not
|
||||
completely decode the length of each individual flag (i.e.
|
||||
TELN conflicts with the T-flag for online-time)
|
||||
Additional flags for ip-nodes are:
|
||||
|
||||
1.1.8.1. IBN[:24554] (Argus: BND[:24554])
|
||||
BinkP protocol
|
||||
|
||||
1.1.8.2. IFC[:60179]
|
||||
Raw protocol as used by ifcico
|
||||
|
||||
1.1.8.3. ITN[:23] (Argus: TEL[:23])
|
||||
Telnet protocol. Some variants of ifcico support Telnet
|
||||
on port 60177, which should be added as additional flag
|
||||
ITN:60177.
|
||||
|
||||
1.1.8.4. IVM[:3141]
|
||||
Vmodem protocol
|
||||
|
||||
1.1.8.5. IP
|
||||
General flag for special protocol specifications, if the
|
||||
flags conforming to 1.1.8.1. to 1.1.8.4. are not relevant.
|
||||
|
||||
1.1.9. Comments on the proposed nodelist flags
|
||||
The additional flagnames in () are supported at this moment
|
||||
by Argus, based on the use in z2r50. But the TEL[NET]-flag
|
||||
stays in conflict with the generally in all zones and
|
||||
regions used T-flag (online time according to FSC-0062).
|
||||
|
||||
|
||||
2. Optional extensions for future use
|
||||
--------------------------------------
|
||||
|
||||
While the above mentioned flags (1.1.8.1 to 1.1.8.4) define a
|
||||
minimum set of operational flags for ip-nodes, several additions
|
||||
are already foreseeable at this moment.
|
||||
|
||||
2.1. Additional sessions_handshake parameters
|
||||
There is at least one program, which supports several
|
||||
transport protocols according to chapter 1.1.8. on a
|
||||
single port. If other programs should imitate this habit,
|
||||
then the following extension to the flag suite 1.1.8.
|
||||
(transport[:port[:handshake]])is advised:
|
||||
|
||||
2.1.1. FTS-0001 session handshake: 1
|
||||
2.1.2. Yoohoo session handshake : Y
|
||||
2.1.3. EMSI sessions handshake : E
|
||||
2.1.4. BinkP sessions handshake : B
|
||||
|
||||
2.2. Non-handshaking protocols
|
||||
While the definitions until this chapter describe direct
|
||||
handshaking sessions with optional password authentification,
|
||||
there are several other methods for the tunneling of fidonet
|
||||
data via the internet available.
|
||||
The setup of these connections does not rely on the nodelist
|
||||
(at this moment of writing), but we can think of standard
|
||||
setup procedures to use the nodelist for configuration of
|
||||
this additional transport methods.
|
||||
Therefore the following flags 2.2.1. to 2.2.4. are advised
|
||||
for at least informational purpose.
|
||||
|
||||
2.2.1. IFT
|
||||
FTP (File Transfer Protocol)
|
||||
|
||||
2.2.2. ITX
|
||||
TransX, an Email based variant
|
||||
|
||||
2.2.3. IUC
|
||||
Uuencoded packet (one packet per message)
|
||||
|
||||
2.2.4. IEM
|
||||
Email based (generally, without exact specification at
|
||||
this moment)
|
||||
|
||||
|
||||
3. Addendum
|
||||
------------
|
||||
|
||||
This proposal is based on a maximum compatibility to generally used
|
||||
definitions and standards within the Fidonet community.
|
||||
Future developments might make additions necessary, if they can not
|
||||
be expressed with the existing set of flags as defined by this FSP.
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
1276
html/misc/jam.html
1276
html/misc/jam.html
File diff suppressed because it is too large
Load Diff
@@ -1,114 +1,114 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" "content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Binkley style outbound with MBSE BBS.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 02-Feb-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<h1>Binkly style outbound documentation for MBSE BBS.</H1>
|
||||
<P>
|
||||
The MBSE BBS outbound directory structure is BinkleyTerm compatible, with
|
||||
domains and point subdirectories (full 5d). There are separate "protected" and
|
||||
"unknown" inbound directories for incoming sessions. Files received during
|
||||
outbound sessions are always placed in the "protected" inbound directory. Only
|
||||
the "protected" inbound directory is processed automatic.
|
||||
<P>
|
||||
|
||||
<P>
|
||||
Note that this is a very simple document and that it is not even finished.
|
||||
<P>
|
||||
<PRE>
|
||||
.pol Poll flag, is handled as crash immediate, the length is always 0 bytes.
|
||||
|
||||
Flow files are files with the full pathnames to the files to send
|
||||
on disk. Names are translated by MBSE BBS to full DOS filenames and
|
||||
paths depending on your setup.
|
||||
If you use it then it is importand that you think about the directory
|
||||
structure to use. See also the documentation about the setup of the
|
||||
<a href="ftpserver.html">ftp server</a>
|
||||
The filenames may be prepended with a special character:
|
||||
# = Truncate file after sent.
|
||||
- or ^ = Kill file after sent.
|
||||
@ = Leave file after sent, this is the default.
|
||||
|
||||
.flo Normal flow file (contains complete filenames to send).
|
||||
.clo Crash flow file.
|
||||
.hlo Hold flow file.
|
||||
.ilo Immediate flow file, overrides CM flag.
|
||||
|
||||
The following are .pkt files, during the mail session they will be
|
||||
renamed to nnnnnnnn.pkt with an unique name and added to the spool
|
||||
file. Messages can allways be added to the outbound as long as the
|
||||
node isn't locked.
|
||||
|
||||
.out Normal .pkt file.
|
||||
.cut Crash .pkt file.
|
||||
.hut Hold .pkt file.
|
||||
.iut Immediate .pkt file.
|
||||
|
||||
It seems that these are subdirectories used by ifpack during packing
|
||||
of mail. These are used for the news/e-mail gate.
|
||||
|
||||
.opk
|
||||
.cpk
|
||||
.hpk
|
||||
.ipk
|
||||
|
||||
|
||||
.req Request file. Contains filenames in ascii with <cr><lf>.
|
||||
|
||||
.su0 Arcmail bundles, the last digit may be any digit or letter.
|
||||
.mo0
|
||||
.tu0
|
||||
.we0
|
||||
.th0
|
||||
.fr0
|
||||
.sa0
|
||||
|
||||
.sts Node status file created by mbcico. These are data files containing
|
||||
three values:
|
||||
1. 'time', this is the last call attempt time (in time_t format).
|
||||
2. 'retries', is the number of retries to try to connect that node. This
|
||||
field is zeroed when the call succeeds or when that node calls in.
|
||||
It is also zeroed when a new poll is created. Currently, mbcico stops
|
||||
calling a node if the counter is higher then 30.
|
||||
3. 'code', is the return code of the last attempt.
|
||||
0 - Successfull call
|
||||
1 - No dialout port available
|
||||
2 - No CONNECT or TCP connect failed
|
||||
3 - Could not reset the modem
|
||||
4 - System is locked
|
||||
5 - Retry time not reached?
|
||||
6 - Fatal error in nodelist lookup
|
||||
7 - Call prohibited by config options
|
||||
8 - Phone number unavailable
|
||||
9 - No free matching port
|
||||
10 - Unused
|
||||
11..29 - Session (handshake) errors.
|
||||
This file is <b>not</b> compatible with the .sts files created by <b>ifcico</b>.</PRE>
|
||||
|
||||
<PRE>
|
||||
.spl Spool file, created by mbcico.
|
||||
|
||||
.bsy Busy file, for locking nodes. The 'pid' of the process who locked that
|
||||
node is inserted into this file. All programs of the MBSE BBS package
|
||||
(and ifcico package) check if the pid exists if a .bsy file is found.
|
||||
If there is no pid found, the lock is a stale lock and is removed.
|
||||
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35">
|
||||
Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Binkley style outbound with MBSE BBS.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 02-Feb-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<h1>Binkly style outbound documentation for MBSE BBS.</H1>
|
||||
<P>
|
||||
The MBSE BBS outbound directory structure is BinkleyTerm compatible, with
|
||||
domains and point subdirectories (full 5d). There are separate "protected" and
|
||||
"unknown" inbound directories for incoming sessions. Files received during
|
||||
outbound sessions are always placed in the "protected" inbound directory. Only
|
||||
the "protected" inbound directory is processed automatic.
|
||||
<P>
|
||||
|
||||
<P>
|
||||
Note that this is a very simple document and that it is not even finished.
|
||||
<P>
|
||||
<PRE>
|
||||
.pol Poll flag, is handled as crash immediate, the length is always 0 bytes.
|
||||
|
||||
Flow files are files with the full pathnames to the files to send
|
||||
on disk. Names are translated by MBSE BBS to full DOS filenames and
|
||||
paths depending on your setup.
|
||||
If you use it then it is importand that you think about the directory
|
||||
structure to use. See also the documentation about the setup of the
|
||||
<a href="ftpserver.html">ftp server</a>
|
||||
The filenames may be prepended with a special character:
|
||||
# = Truncate file after sent.
|
||||
- or ^ = Kill file after sent.
|
||||
@ = Leave file after sent, this is the default.
|
||||
|
||||
.flo Normal flow file (contains complete filenames to send).
|
||||
.clo Crash flow file.
|
||||
.hlo Hold flow file.
|
||||
.ilo Immediate flow file, overrides CM flag.
|
||||
|
||||
The following are .pkt files, during the mail session they will be
|
||||
renamed to nnnnnnnn.pkt with an unique name and added to the spool
|
||||
file. Messages can allways be added to the outbound as long as the
|
||||
node isn't locked.
|
||||
|
||||
.out Normal .pkt file.
|
||||
.cut Crash .pkt file.
|
||||
.hut Hold .pkt file.
|
||||
.iut Immediate .pkt file.
|
||||
|
||||
It seems that these are subdirectories used by ifpack during packing
|
||||
of mail. These are used for the news/e-mail gate.
|
||||
|
||||
.opk
|
||||
.cpk
|
||||
.hpk
|
||||
.ipk
|
||||
|
||||
|
||||
.req Request file. Contains filenames in ascii with <cr><lf>.
|
||||
|
||||
.su0 Arcmail bundles, the last digit may be any digit or letter.
|
||||
.mo0
|
||||
.tu0
|
||||
.we0
|
||||
.th0
|
||||
.fr0
|
||||
.sa0
|
||||
|
||||
.sts Node status file created by mbcico. These are data files containing
|
||||
three values:
|
||||
1. 'time', this is the last call attempt time (in time_t format).
|
||||
2. 'retries', is the number of retries to try to connect that node. This
|
||||
field is zeroed when the call succeeds or when that node calls in.
|
||||
It is also zeroed when a new poll is created. Currently, mbcico stops
|
||||
calling a node if the counter is higher then 30.
|
||||
3. 'code', is the return code of the last attempt.
|
||||
0 - Successfull call
|
||||
1 - No dialout port available
|
||||
2 - No CONNECT or TCP connect failed
|
||||
3 - Could not reset the modem
|
||||
4 - System is locked
|
||||
5 - Retry time not reached?
|
||||
6 - Fatal error in nodelist lookup
|
||||
7 - Call prohibited by config options
|
||||
8 - Phone number unavailable
|
||||
9 - No free matching port
|
||||
10 - Unused
|
||||
11..29 - Session (handshake) errors.
|
||||
This file is <b>not</b> compatible with the .sts files created by <b>ifcico</b>.</PRE>
|
||||
|
||||
<PRE>
|
||||
.spl Spool file, created by mbcico.
|
||||
|
||||
.bsy Busy file, for locking nodes. The 'pid' of the process who locked that
|
||||
node is inserted into this file. All programs of the MBSE BBS package
|
||||
(and ifcico package) check if the pid exists if a .bsy file is found.
|
||||
If there is no pid found, the lock is a stale lock and is removed.
|
||||
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35">
|
||||
Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
@@ -1,63 +1,63 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" "content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Semafore files with MBSE BBS.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 27-jul-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1>Semafore files with MBSE BBS.</H1>
|
||||
|
||||
The directory $MBSE_ROOT/sema is the hardcoded semafore directory where all
|
||||
semafore's must be created, tested and removed. When the system is booting,
|
||||
the init script will erase all semafore's just before the BBS is started.
|
||||
This description is valid from MBSE BBS v0.33.18 and newer.
|
||||
|
||||
<PRE>
|
||||
zmh Purpose: to mark the state of Zone Mail Hour.
|
||||
Created by "mbtask" at the start of Zone Mail Hour.
|
||||
Removed by "mbtask" at the end of Zone Mail Hour.
|
||||
|
||||
upsalarm Purpose: Signal that the system is running on battery power.
|
||||
Created and removed by UPS software.
|
||||
Checked by mbtask to suspend processing.
|
||||
Checked by mbfido to stop processing.
|
||||
|
||||
upsdown Purpose: Signal that the system will go down on low battery.
|
||||
Created and removed by UPS software.
|
||||
Checked by mbtask to go down.
|
||||
Checked by several scripts and "mbstat wait".
|
||||
|
||||
newnews Purpose: Signal that there are new articles on the news server.
|
||||
Checked by mbtask to start news processing.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
mailout Purpose: Signal that there is mail posted in the message base.
|
||||
Checked by mbtask to start scan the message base.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
mailin Purpose: Signal that there is new mail in the inbound.
|
||||
Checked by mbtask to start the tosser.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
scanout Purpose: Signal that the outbound must be rescanned.
|
||||
Checked by mbtask to check the outbound.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
mbtask.last Purpose: A timestamp created and touched by "mbtask" every
|
||||
minute so you can check it is running.
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||
<META http-equiv="Content-Style-Type" content="text/css">
|
||||
<META name="author" lang="en" content="Michiel Broek">
|
||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||
<TITLE>Semafore files with MBSE BBS.</TITLE>
|
||||
<LINK rel=stylesheet HREF="../manual.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 27-jul-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1>Semafore files with MBSE BBS.</H1>
|
||||
|
||||
The directory $MBSE_ROOT/sema is the hardcoded semafore directory where all
|
||||
semafore's must be created, tested and removed. When the system is booting,
|
||||
the init script will erase all semafore's just before the BBS is started.
|
||||
This description is valid from MBSE BBS v0.33.18 and newer.
|
||||
|
||||
<PRE>
|
||||
zmh Purpose: to mark the state of Zone Mail Hour.
|
||||
Created by "mbtask" at the start of Zone Mail Hour.
|
||||
Removed by "mbtask" at the end of Zone Mail Hour.
|
||||
|
||||
upsalarm Purpose: Signal that the system is running on battery power.
|
||||
Created and removed by UPS software.
|
||||
Checked by mbtask to suspend processing.
|
||||
Checked by mbfido to stop processing.
|
||||
|
||||
upsdown Purpose: Signal that the system will go down on low battery.
|
||||
Created and removed by UPS software.
|
||||
Checked by mbtask to go down.
|
||||
Checked by several scripts and "mbstat wait".
|
||||
|
||||
newnews Purpose: Signal that there are new articles on the news server.
|
||||
Checked by mbtask to start news processing.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
mailout Purpose: Signal that there is mail posted in the message base.
|
||||
Checked by mbtask to start scan the message base.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
mailin Purpose: Signal that there is new mail in the inbound.
|
||||
Checked by mbtask to start the tosser.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
scanout Purpose: Signal that the outbound must be rescanned.
|
||||
Checked by mbtask to check the outbound.
|
||||
Removed by mbtask as soon as it is detected.
|
||||
|
||||
mbtask.last Purpose: A timestamp created and touched by "mbtask" every
|
||||
minute so you can check it is running.
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
@@ -1,61 +1,61 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>System load and the usleep() call.</TITLE>
|
||||
</HEAD>
|
||||
|
||||
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
||||
<BODY
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#000080"
|
||||
ALINK="#FF0000"
|
||||
>
|
||||
<PRE>
|
||||
usleep.doc
|
||||
|
||||
|
||||
At some time when developping MBSE BBS I decided that background utilities
|
||||
did't need full speed to do their jobs. BBS utilities under DOS needed
|
||||
to run as fast as possible because you needed to bring the bbs down to run
|
||||
these programs and users couldn't login during that time.
|
||||
|
||||
Starting with mball, the allfiles creator, I inserted code that does usleep(1)
|
||||
after each 5 processed files. The 1 microsecond is not really the time the
|
||||
program pauses, it's probably a lot longer. I think this depends on the
|
||||
hardware type, (Intel, Sparc, Alpha etc) how long Linux will really suspends
|
||||
executing the utility.
|
||||
|
||||
The program speed downgrade at the development machine that mball needed was
|
||||
3 times the original exection time, while system loading stayed under 30%.
|
||||
At that time the development machine is an 486DX2-66 with a Seagate ST32151N
|
||||
SCSI harddisk.
|
||||
|
||||
The extra usleep code is only active if you run these utils with the -quiet
|
||||
switch and when this is set in mbsetup. See menu 1->5.
|
||||
With this switch, the program is mostly run by cron. If you onmit
|
||||
this switch, this is probably when you start the program manually, it will
|
||||
then always run at full speed, no matter what the setting in mbsetup is.
|
||||
|
||||
If you have a fast system or don't care that the performance of your system
|
||||
drops because of background processing, you can turn this future off with
|
||||
mbsetup in the global section. (menu 1->5).
|
||||
|
||||
Remember, if you have a PII-400 MMX or so with IDE disks, you may still have
|
||||
performance problems and need to set that switch to yes. There is only one
|
||||
way to find out if you need it.
|
||||
|
||||
Well, actually, I tested this on a Dell Latitude PII-266, setting the switch to
|
||||
yes gave better performance then no. Why? The CPU has more time for the slow
|
||||
IDE disk. With the slow switch on programs runs even faster then with the switch
|
||||
off.
|
||||
|
||||
Michiel.
|
||||
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>System load and the usleep() call.</TITLE>
|
||||
</HEAD>
|
||||
|
||||
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
||||
<BODY
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#000080"
|
||||
ALINK="#FF0000"
|
||||
>
|
||||
<PRE>
|
||||
usleep.doc
|
||||
|
||||
|
||||
At some time when developping MBSE BBS I decided that background utilities
|
||||
did't need full speed to do their jobs. BBS utilities under DOS needed
|
||||
to run as fast as possible because you needed to bring the bbs down to run
|
||||
these programs and users couldn't login during that time.
|
||||
|
||||
Starting with mball, the allfiles creator, I inserted code that does usleep(1)
|
||||
after each 5 processed files. The 1 microsecond is not really the time the
|
||||
program pauses, it's probably a lot longer. I think this depends on the
|
||||
hardware type, (Intel, Sparc, Alpha etc) how long Linux will really suspends
|
||||
executing the utility.
|
||||
|
||||
The program speed downgrade at the development machine that mball needed was
|
||||
3 times the original exection time, while system loading stayed under 30%.
|
||||
At that time the development machine is an 486DX2-66 with a Seagate ST32151N
|
||||
SCSI harddisk.
|
||||
|
||||
The extra usleep code is only active if you run these utils with the -quiet
|
||||
switch and when this is set in mbsetup. See menu 1->5.
|
||||
With this switch, the program is mostly run by cron. If you onmit
|
||||
this switch, this is probably when you start the program manually, it will
|
||||
then always run at full speed, no matter what the setting in mbsetup is.
|
||||
|
||||
If you have a fast system or don't care that the performance of your system
|
||||
drops because of background processing, you can turn this future off with
|
||||
mbsetup in the global section. (menu 1->5).
|
||||
|
||||
Remember, if you have a PII-400 MMX or so with IDE disks, you may still have
|
||||
performance problems and need to set that switch to yes. There is only one
|
||||
way to find out if you need it.
|
||||
|
||||
Well, actually, I tested this on a Dell Latitude PII-266, setting the switch to
|
||||
yes gave better performance then no. Why? The CPU has more time for the slow
|
||||
IDE disk. With the slow switch on programs runs even faster then with the switch
|
||||
off.
|
||||
|
||||
Michiel.
|
||||
|
||||
</PRE>
|
||||
|
||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user