REPORTING A BUG
If you observe odd behaviour of this server, which is not of what you
believe to be correct, please contact problems@ftp.funet.fi and in the
report have attached a session log which shows the wrong functionality.
However, check at first what we state about "Usage Restrictions" !
Such log should start from your FTP session startup, and it should contain:
-
Descriptions about your (computing-) environment relevant
with attempted FTP access;
- Maker and model of the computer where you ran your
FTP session,
- TCP/IP software model and maker (quite many system do
not come with builtin TCP/IP -- VMS-machines are one
such example.)
- UNEDITED (verbose, unabridged) session transcript showing
EVERYTHING you sent to this system, and what were the responses.
Note: Reports about corrupted files belong to archive area keepers; they
handle those files; "problems" handles the server subsystem.
Note to VMS users with UCX earlier than V2.0:
YOUR SYSTEM IS FAULTY
From gatekeeper.dec.com -ftp login banner:
If you are connecting to gatekeeper from a VMS system running a version of
UCX earlier than V2.0, a bug in UCX will prevent the automatic login from
working. To get around this, wait for the message that says:
%UCX-E-FTP_LOGREJ, Login request rejected
and then log in by hand with the "login" command at the "FTP>" prompt. You
should also consider upgrading to the latest version of UCX.
- Bugs/problems relating to ARCHIVED MATERIAL:
- Select by list under: `Contacts about material in here'
- Uploads:
-
Select by list under: `Contacts about material in here'.
If no suitable one can be found, check also /README.UPLOADER.
In outmost despair (ONLY then! postmaster@ftp.funet.fi)
- Bugs/problems relating to archie:
-
<archie-admin@nic.funet.fi>
- Bugs/problems relating to other parts of system software:
-
Problems group: <problems@ftp.funet.fi>
("system software" does not mean anything under /pub/")
If you can get /README without trouble, don't contact <problems>
but one of the area administration aliases.