Updated docs and FAQ
This commit is contained in:
Michiel Broek
parent
7cd927c877
commit
6e30d29ce4
157
html/faq.html
157
html/faq.html
@ -3,31 +3,21 @@
|
||||
<head>
|
||||
<!-- $Id$ -->
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
|
||||
<meta http-equiv="Content-Style-Type" content="text/css">
|
||||
|
||||
<meta name="GENERATOR" content="vi handcraft">
|
||||
|
||||
<meta name="author" lang="en" content="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>MBSE BBS FAQ & Howto</title>
|
||||
|
||||
<link rel="stylesheet" href="manual.css">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<blockquote>
|
||||
<div align="Center">
|
||||
<h1>MBSE BBS FAQ and Howto.</h1>
|
||||
</div>
|
||||
|
||||
<div align="Center"><h1>MBSE BBS FAQ and Howto.</h1></div>
|
||||
<hr>
|
||||
<div align="Right">
|
||||
<h5>Last updated 10-Jul-2002</h5>
|
||||
</div>
|
||||
<div align="Right"><h5>Last updated 28-Oct-2002</h5></div>
|
||||
|
||||
<pre> Author: P.E. Kimble aka King Kimerud<br> kimerud@bayhaus.org<br> </pre>
|
||||
Introduction
|
||||
@ -88,11 +78,9 @@ out.</a>
|
||||
</li>
|
||||
|
||||
<ol>
|
||||
<li><a href="#3.1">Posting newsmessages to the newsserver fails.</a>
|
||||
</li>
|
||||
<li><a href="#3.2">FTP fidonet feeds how-to.</a>
|
||||
</li>
|
||||
|
||||
<li><a href="#3.1">Posting newsmessages to the newsserver fails.</a></li>
|
||||
<li><a href="#3.2">FTP fidonet feeds how-to.</a></li>
|
||||
<li><a href="#3.3">Polling a internet node fails</a></li>
|
||||
</ol>
|
||||
|
||||
<p> </p>
|
||||
@ -359,10 +347,7 @@ It is meant only as a description for the filearea. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="Top">A 2.5</td>
|
||||
<td> No, not directly. It is a matter of using scripts to translate
|
||||
the .*lo (*.flo, *.clo, *.dlo, *.ilo) files for each node, and copying the
|
||||
node's outbound files to their respective directory. <a href="#2.5">Refer
|
||||
to 3.2.</a>
|
||||
<td> Yes, but only the passive side. <a href="#2.5">Refer to 3.2.</a>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -403,54 +388,106 @@ Set this flag in mbsetup 1.15.5 </td>
|
||||
<tr>
|
||||
<td valign="Top">A 3.2</td>
|
||||
<td>
|
||||
Follow the next steps to setup your system for FTP clients.
|
||||
<ol>
|
||||
<li>In mbsetup menu 1.4.12:2, remove any reference to a DOS translation path.
|
||||
</li>
|
||||
<li> In mbsetup menu 1.4.12:3, remove any reference to a DOS translation
|
||||
path. </li>
|
||||
</ol>
|
||||
This will give you a "True" path to your files directory where mbcico tosses
|
||||
the inbound files.
|
||||
<ol>
|
||||
<li value="3"> Ftp Script for running a ftp feed with MBSE.<br>
|
||||
NOTE: Gracefully contributed by Janis Kacht <janis@filegate.net>
|
||||
<p> This script does not delete or change the .flo file. It reads
|
||||
it in and creates a new script that will be used to move and copy the files
|
||||
to the user's outbound directory you specify on the command line. Just call
|
||||
this script, then call the finalflo.sh script with the directory name where
|
||||
the files should be PUT, like: </p>
|
||||
<p> </p>
|
||||
<pre>parseflo <enter><br>finalflo.sh /home/fido/jdoe/out <enter><br></pre>
|
||||
<li>As root, add a new group to your system: <b>groupadd bbsftp</b>.
|
||||
<li>Make sure there is a directory /opt/mbse/var/bbsftp. This directory
|
||||
should be owned by mbse, group bbs and have mode 0775.
|
||||
<li>Add an invalid shell to /etc/shells, /usr/bin/false is good.
|
||||
<li>Install an FTP server, the examples here are for ProFTPD.
|
||||
<li>In /etc/proftpd.conf make sure there are the following lines:
|
||||
<pre>
|
||||
# Anonymous ftp and members of group bbsftp have a chroot environment.
|
||||
DefaultRoot ~ bbsftp
|
||||
</pre>
|
||||
This will make sure that users who are member of the bbsftp group have
|
||||
a chrooted directory structure for their ftp directories.
|
||||
Also make sure the line Umask 022 is changed to Umask 002.
|
||||
<li>Add a username for the node you whish to give an FTP feed. Use the
|
||||
following as root:
|
||||
<pre>
|
||||
useradd -g bbs -G bbsftp -d /opt/mbse/var/bbsftp/username
|
||||
-s /usr/bin/false -c "FTP Account for username" -m username
|
||||
</pre>
|
||||
Note: this is one line!
|
||||
There will now be a user added and have a home directory of
|
||||
/opt/mbse/var/bbsftp/username. Make sure that directory has permission
|
||||
0775 or 0770. Create in the username directory two other directories,
|
||||
inbound and outbound. They must be owned by the user and be a member of
|
||||
group bbs and have mode 0775. The modes 077x are needed because the
|
||||
user and mbse must be able to read and write to these directories.
|
||||
<li>Try to login with ftp from some other system with the choosen
|
||||
username and his password and check the changes until now. You should
|
||||
not be able to escape from the directories of this user and you should
|
||||
be able to upload files, download and delete files. Check also if you
|
||||
uploaded a file if user mbse can delete that file and also put a file
|
||||
in the users ftp directory as user mbse, and check that you can
|
||||
download and delete is as ftp user.
|
||||
<li>
|
||||
Make sure for the node you want to change there is no mail left in the
|
||||
outbound.
|
||||
Now start mbsetup, menu 7, open the setup of the node that will use
|
||||
ftp. In screen 3, items 7 and 8, set these to Directory. Now enter
|
||||
screen 8, here you will setup the directory session.
|
||||
<pre>
|
||||
7.8 EDIT NODE DIRECTORY SESSION
|
||||
|
||||
<p> You will need a full path to the flo file in the "test" line
|
||||
below and change the name of the flo file (it's not going to be 00000063.flo)
|
||||
Uncomment the "if test" line, and also uncomment the last line (fi) </p>
|
||||
<pre>#!/bin/sh<br>if test -e /opt/mbse/mail/outbound/00000063.flo ; then<br> cat 00000063.flo | sed 's/\/home/cp \/home/' > newflo.txt<br> cat newflo.txt | sed 's/\^\cp \/home/mv \/home/'> newflo2.txt<br> cat newflo2.txt | sed 's/$/ \$1/' > finalflo.sh<br>fi<br></pre>
|
||||
Outbound settings
|
||||
1. Files path /opt/mbse/var/bbsftp/username/outbound
|
||||
2. Check for lock Yes 3. Wait clear lock No
|
||||
4. Check lockfile /opt/mbse/var/bbsftp/username/lock.bsy
|
||||
5. Create lock Yes
|
||||
6. Create lockfile /opt/mbse/var/bbsftp/username/lock.bsy
|
||||
|
||||
<p> here's what finalflo.sh looks like, $1 is a variable for
|
||||
the directory name you specify on the command line, or in a cron script:
|
||||
</p>
|
||||
<pre>cp /home/ftp/pub/filegate/fg_worf/filegate.zxx $1<br>mv /opt/mbse/mail/outbound/00000063/dooqi39k.tic $1<br>cp /home/ftp/pub/filegate/ss_areas/ss_areas.zip $1<br>mv /opt/mbse/mail/outbound/00000063/dooqi39l.tic $1<br>cp /home/ftp/pub/filebone/admin/backbone/backbone.z1b $1<br>mv /opt/mbse/mail/outbound/00000063/dooqi39m.tic $1<br></pre>
|
||||
|
||||
<p> Janis Kracht can not and will not be held liable if harm
|
||||
is done to your computer system due to any use of this script, either directly
|
||||
or indirectly. This script works perfectly when instructions are followed,
|
||||
and the correct directories are substitiuted. How it will affect your system,
|
||||
is the responsiblity of the system administrator! </p>
|
||||
</li>
|
||||
<li> Do not forget to test this setup. It has work fine on my
|
||||
system, but nothing works the way it should the first time out of the box!
|
||||
Pay close attention to the ftp script and directories you enter. It seems
|
||||
as if 75% of the problems experinced with this sed script is due to improper
|
||||
outbound directories </li>
|
||||
Inbound settings
|
||||
7. Files path /opt/mbse/var/bbsftp/username/inbound
|
||||
8. Check for lock Yes 9. Wait clear lock Yes
|
||||
10. Check lockfile /opt/mbse/var/bbsftp/username/lock.bsy
|
||||
11. Create lock Yes
|
||||
12. Create lockfile /opt/mbse/var/bbsftp/username/lock.bsy
|
||||
</pre>
|
||||
Save this and you are ready.
|
||||
<li>A final note, since this user is in group bbs and not in the bbs
|
||||
userdatabase he can never telnet to your system with this account and
|
||||
get a shell. The user doesn't even have a valid shell.
|
||||
</ol>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<a href="#_Inetsetup"><img src="images/hand.up.gif" border="0" alt="Up">
|
||||
</a>
|
||||
|
||||
<a href="#_Inetsetup"><img src="images/hand.up.gif" border="0" alt="Up"></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<tr>
|
||||
<td width="50" valign="Top"><a name="3.3">Q 3.3</a>
|
||||
</td>
|
||||
<td>Polling a internet node fails.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="Top">A 3.3</td>
|
||||
<td>
|
||||
There are several reasons why mbcico refuses to call an internet node, most
|
||||
problems are nodelist related. A internet node with binkp protocol should be
|
||||
listed with the flags CM,IBN before mbcico will make a call. Also, in the
|
||||
nodelist system name field there should be the hosts full qualified
|
||||
domainname so that mbcico can get that node's IP address. If one of these
|
||||
items are missing, the node will not be called. To correct this problem there
|
||||
are two options, make sure the node is listed with a dns name and proper
|
||||
flags in the nodelist. The second option is to add a setup record for that
|
||||
node and fill in the nodelist override fields. You can find these in menu
|
||||
7.3, item 5 can be filled with the nodelist flags, ie. CM,IBN and item 6 can
|
||||
be used to give that node's fdn or IP address.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<a href="#_Inetsetup"><img src="images/hand.up.gif" border="0" alt="Up"></a>
|
||||
</p>
|
||||
|
||||
<p></p>
|
||||
<hr>
|
||||
<h3><a name="4">4. BBS setup.</a>
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<div align="right"><h5>Last update 28-Sep-2002</h5></div>
|
||||
<div align="right"><h5>Last update 28-Oct-2002</h5></div>
|
||||
|
||||
<div align="center"><H1>MBSE BBS Setup - Global Setup</H1></div>
|
||||
<P>
|
||||
@ -237,17 +237,19 @@ will be updated automatic.
|
||||
<strong>Max. dupes </strong>The maximum number of entries in dupe database
|
||||
<strong>Keep date </strong>Keep original filedate
|
||||
<strong>Keep netm </strong>Keep sent netmails
|
||||
<strong>Res future </strong>Reset dates in the future
|
||||
<strong>Loc resp </strong>Respond to local created filefind messages
|
||||
<strong>Repl ext </strong>Replace filename extension with .* before filesearch
|
||||
<strong>Plus all </strong>Allow filemgr +all command
|
||||
<strong>Notify </strong>Allow filemgr notify=on/off command
|
||||
<strong>Passwd </strong>Allow filemgr passwd command
|
||||
<strong>Passwd </strong>Allow filemgr/areamgr passwd command
|
||||
<strong>Message </strong>Allow filemgr message=on/off command
|
||||
<strong>Tic on/off </strong>Allow filemgr tic=on/off command
|
||||
<strong>Pause </strong>Allow filemgr pause/resume commands
|
||||
</pre><p>
|
||||
When you change one of the <b>Allow filemgr</b> settings, you also need to edit
|
||||
the file /opt/mbse/english/macro/filemgr.help to reflect the new settings.
|
||||
Default all these switches are set to Yes.
|
||||
|
||||
<p>
|
||||
<h3>1.14. Edit Fidonet mail and echomail processing.</h3>
|
||||
<p>
|
||||
Note that the first 2 mailboards must also exist in the normal mail areas if
|
||||
@ -281,7 +283,15 @@ it is necessary.<br>
|
||||
<strong>4d address </strong>Use 4d. addressing (not needed you only use MBSE BBS)
|
||||
<strong>Split at </strong>Gently split messages after n KBytes (12..60)
|
||||
<strong>Force at </strong>Force split of messages after n KBytes (16..63)
|
||||
<strong>Plus all </strong>Allow areamgr +all command
|
||||
<strong>Notify </strong>Allow areamgr notify=on/off command
|
||||
<strong>Passwd </strong>Allow areamgr/filemgr passwd command
|
||||
<strong>Pause </strong>Allow areamgr pause/resume commands
|
||||
</pre><p>
|
||||
When you change one of the <b>Allow areamgr</b> settings, you also need to edit
|
||||
the file /opt/mbse/english/macro/areamgr.help to reflect the new settings.
|
||||
Default all these switches are set to Yes.
|
||||
<P>
|
||||
A note about the splitting of messages. Some tossers can't handle
|
||||
messages greater than 16 KBytes, these tossers are rare these days. Most
|
||||
tossers can handle messages of 32 KBytes. To set these values on the safe
|
||||
|
||||
Reference in New Issue
Block a user