Hangar.La tienda de software del Amiga

AmiTCP_ups10

Nice little AmiTCP file transmission program

Short:        Nice little AmiTCP file transmission program
Author:       ???, amiga port by ch@irb.informatik.uni-dortmund.de
Uploader:     ch irb informatik uni-dortmund de
Type:         comm/net
Architecture: m68k-amigaos

Hello Netters,

I wanted to know how difficult it is to create a daemon suitable for
AmiTCP. I liked the little program "ups" we use at the university of
Dortmund for sending files between users and so I took the source
to my amiga.
Here's the result. 

Be warned:
	I didn't take much effort in making a clean port but I hope I
	didn't introduce much new bugs :-)


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! But as ever: You got what you paid for, use at your own risk.!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Take a look at the original README to see what ups does.

Here a short summary:
1. Send the files 'a', 'b' and 'c' to a <user> on <host>:
	ups user@host a b c
2. Look for arrived files
	ups -q
3. Receive files
	ups
	
The port was done using SAS 6.3 and AmiTCP 2.0.

Installation on amitcp

	1)  Add ups to the table of known ports in amitcp:db/services as follows:

	ups	600/tcp

	2)  Add ups to the inetd configuration file amitcp:db/inetd.conf:

	ups	stream	tcp	nowait	root	amitcp:bin/upsd	upsd

	3) Copy ups, upsd and ups-sendmail to amitcp:bin.

	4) Set USERNAME in your user-startup to your login name.
	   Set UPS_USERS to a colon separated list of users able to 
	   receive files via ups.

	   I use:
		setenv USERNAME alph
		setenv UPS_USERS alph:ch

	5) Make an "assign ups-spool: <somewhere>" to your incoming
	   spool directory.
	
Changes to the un*x version:
	- Since there's no semi-official port of /etc/password stuff I
	  made the following assumptions:
	  Sender:
		The name of the sender is obtained from the
		environment variable USERNAME, the name of the
		host from HOSTNAME.
	  Receiver:
		The ups daemon will accept incoming files 
		only for users listed in UPS_USERS, e.g. 
		"ups alph@alph3000 mytreasure" will only be legal if
		UPS_USERS contains 'alph' on the host alph3000.

	- Since there's no semi-official port of /etc/aliases I disabed
	  the alias feature of ups.
	
	- On un*x boxes ups uses mail to inform the user about
	  new files. To keep it simple I include a fake sendmail
	  (ups-sendmail) which just opens a Console-Window
	  containing the mail normally send :-)
	  You may replace ups-sendmail with your own program.
	  It should accept sendmail-like parameters and will get it's
	  Input via stdin.

Notes:
	- When sending files between amigas only un*x-like protection bits
	  will be preserved. Sending format is un*x-format to be
	  compatible with the un*x version.

	  It should be easy to enhance the protocol to identify
	  an amiga on the other side and behave according to that.

	- I'm using my s_socket layer instead of changing the read/write
	  calls because of pure lazyness.:-) (I used it extensively in my
	  port of ncftp)

As I said before I didn't put much effort in changing the ups source
so you're welcome to proceed.

I hope you enjoy it,
	
	Carsten Heyl

You may try to reach me via email at ch@irb.informatik.uni-dortmund.de.


Gratis

Descargar 69 KB

Desde el Amiga: abre Hangar y busca AmiTCP_ups10.

Autor???, amiga port by ch@irb.informatik.uni-dortmund.de
Categoríacomm/tcp
Tamaño69 KB
Param68k-amigaos
OrigenAminet