Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.SYSOP   33888
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   24094
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   15795/30874
FIDONEWS_OLD4   22912/37224
FIDO_SYSOP   12852
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4393
FN_SYSOP   41678
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13598
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16069
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22090
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   924
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4786
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1121
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   3205
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13258
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2056
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4288
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   32677
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2053
DOS_INTERNET   0/196
duplikat   6002
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
Möte FIDONEWS_OLD4, 37224 texter
 lista första sista föregående nästa
Text 22255, 232 rader
Skriven 2015-03-30 00:35:42 av FidoNews Robot (2:2/2.0)
Ärende: FidoNews 32:13 [03/08]: Ftsc Information
================================================
  -------------------------------------------------------------------
  |12|13|14|15|16|17|18|19|20|21|22|23|00|01|02|03|04|05|06|07|08|09|
  -------------------------------------------------------------------
i |xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|
c |--|--|--|--|--|--|--|--|--|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|--|
d |--|--|--|--|--|--|--|--|--|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|--|--|--|
f |--|--|--|--|--|--|--|--|--|xx|xx|xx|xx|xx|xx|xx|xx|xx|xx|--|--|--|
h |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
  -------------------------------------------------------------------

  3.4. Differences in flow and reduced flow files.

        "Real" flow file means that the system has a portion of
        information to be sent while a reduced flow file only
        expresses a desire to make a poll.

        Thus if a mailer detects a flow file in the directory, it
        must determine whether this is a real flow file or just a
        control file.

        If it is a real flow file the mailer must make a poll accor-
        ding to the flavour, send information to the remote according
        to the type of flow file and delete the flow file after
        sending all information. The mailer should not wait for the
        end of the session when deleting the flow file.

        Thus if a session is terminated accidentally or deliberately
        after sending the flow file information the mailer will return
        to its previous state without a priority flow file in the
        outbound.

        If it is a reduced flow file the mailer must make a poll
        according its flavour. The mailer has nothing to send from the
        control file and it must delete the flow file after the
        successful end of session.

        Thus if a session is terminated accidentally or deliberately
        while sending information, the mailer will return to its
        previous state with the priority flow file in the outbound.

        That is why it is not a good idea to lock flow files during
        the session.

4. File Requests
----------------

  4.1   File request files are named using the same method as flow
        files, with an extension of req. The format of request files
        is documented in FTS-0006. File requests have no flavour on
        their own. They DO NOT initiate a poll to the remote system,
        and must be accompanied by a [reduced] flow file. File
        requests may have additional restrictions (for example,
        based on Nodelist flags or ZMH restrictions) specific to the
        request. Normally this file is deleted after receiving the
        requested files.

        As with NetMail flow files, during a session this file must
        be dynamically renamed at the moment of sending to a remote
        system with a unique name and extension of req.


5. Control files
----------------
  5.1.  bsy (busy) control file

        A bsy is a main control file that must be used by any software
        dealing with flow files in BSO. It is named the same way as
        the flow file but with the extension ".bsy".

        Any software must check this file before doing any changes
        in flow files. If a bsy file exists all changes are prohibited
        in any corresponding flow files. What the software must do in
        this case is implementation dependent.

        If a bsy file does not exist software must create it, ensure
        that it was successfully created, and then work with the flow
        files. After completing the job, software must delete the bsy
        file.

        Note to software developers:
        The most common way to create a file in many languages (eg.
        ReWrite, fopen) also quietly overwrites an existing file, so
        there's a race condition between checking, creating and
        checking. Care must be taken to use the right function and/or
        the right options to get the correct behaviour.

        During the session and before sending information from flow
        files the mailer creates the list of all AKAs presented by the
        remote system. The mailer must then check bsy files
        corresponding to the list. If a bsy file is detected the
        corresponding AKA is removed from the list. If all AKAs are
        removed due to this procedure, the session must be terminated
        with an appropriate diagnostic message.

        If a bsy file for the AKA is not present the mailer must
        create it. A bsy file is created by the mailer only after
        a successful connection with the remote mailer.

        After session - successful or not - the mailer must delete all
        created bsy files.

        After restoring the system due to a crash it is recommended to
        run a simple routine to delete all bsy files in all outbounds
        before starting any software dealing with BSO.

        It is also recommended to check the age of bsy files. It is
        reasonable to ignore and delete bsy files with an age more
        than the maximum estimated time of session multiplied on 2.
        An appropriate diagnostic message may be produced in this
        case.

        For information purposes a bsy file may contain one line of
        PID information (less than 70 characters).

  5.2.  csy (call) control file

        This control file is created by a mailer when it decides
        to make poll to remote system. It is named the same way as a
        flow file but with the extension ".csy". A csy file is valid
        only for another mailer working together on the same system.
        Note that the remark regarding race conditions when creating a
        bsy file, also applies when creating a csy file.

        csy files are created for all remote AKAs as shown in the
        mailer config.

        The presence of a csy file corresponding to any remote AKA
        indicates that the mailer must stop trying to poll the remote
        system regardless of the presence of flow files.

        After a session - successful or not - and after an unsuccess-
        ful try the mailer must delete all created csy files.

        After restoring a system due to a crash it is recommended to
        run a simple routine to delete all csy files in all outbounds
        before starting any software dealing with BSO.

        It is also recommended to check the age of csy files. It is
        reasonable to ignore and delete csy files with an age more
        than the maximum estimated time of a session multiplied by 2.
        An appropriate diagnostic message may be produced in this
        case.

        For information purposes, a csy file may contain one line of
        PID information (less than 70 characters).

  5.3.  hld (hold) control file

        This control file is created by a mailer or other software
        when it decides to stop trying poll a remote system.
        hld file is meaningful only for mailers. It is named the same
        way as a flow file but with the extension ".hld".

        An existing hld file is either replaced by a new one or
        edited.

        A hld file must contain a one line string with the expiration
        of the hold period expressed in UNIX-time.

        The presence an hld file corresponding to any remote AKA
        indicates that the mailer must check the content before trying
        to poll the remote system. If the expiration time is in the
        future, the mailer must stop trying to poll the remote system
        regardless of the presence of any flow files.

        The presence and content of an hld file must be checked before
        each attempt to create a poll.

        If software finds an hld file with an expiration time in past,
        it must delete that hld file.

        For information purposes the second line of an hld file may
        contain one line of PID information. (Less than 70 characters)

  5.3.  try control file
        This control file is created by a mailer when a connect
        attempt is finished - successful or not. It is named the same
        way as a flow file but with the extension ".try".

        An existing try file is replaced by a new one.

        A try file must contain one line string with a diagnostic
        message. It is for information purposes only.

        For information purposes the second line of a try file may
        contain one line of PID information. ( < 70 characters)


A. References
-------------

  [FTS-0001] A Basic FidoNet(r) Technical Standard
             Randy Bush, 30 Sep 95.

  [FTS-0006] YOOHOO and YOOHOO/2U2
             Vince Perriello, 30 Nov 1991.

             T-Mail. Reference Manual
             Andy Elkin, 1997.

             BinkleyTerm. Reference Manual
             1987-1996 Bit Bucket Software, Co.


B. Contact Data
---------------

   Igor Romanovsky
   Fidonet:  2:5022/60
   E-mail:   Igor.Romanovsky@tula.net
   Administrator
   Fidonet: 2:2/20
   E-mail: administrator@ftsc.org


C. History
----------

   This document is based on FSP-1034 by Igor Romanovsky. Some minor
   technical modifications were made by Markus Reschke, Fred Riccio
   and other FTSC members. Grammar and typographical corrections were
   made by Dallas Hinton and others.


   Rev.1, 2014-11-09: Initial Release.
   Rev.2, 2015-03-29: Added section on file requests, fixed typos.
                      Minor reformatting.

-----------------------------------------------------------------

--- Azure/NewsPrep 3.0
 * Origin: Home of the Fidonews (2:2/2.0)