Subject: [netatalk-admins] Clarification on multiple AFP/TCP servers.
From: Duncan Sinclair (sinclair@dis.strath.ac.uk)
Date: Fri Jul 11 1997 - 13:48:57 EDT
Hi,
Based on "a sun"'s comments (sorry, I don't know your actual name),
it seems you can't run two afpd servers on the same machine without
one having to be given a non-standard port.
When you have AppleTalk access to the server this is not a problem,
as the Chooser details (NBP stuff) will point to the correct port.
But in the case of running a second server which you want access to
over an IP-only network, I guess, too bad.
Solutions would involve things like virtual interfaces - giving
multiple IP (and DDP?) addresses or different internet names for
the server which it can tell apart - but only if the protocol
supports it.
I, myself, like the idea of being able to run multiple servers on the
one machine, as it allows me to separate logically different services.
It also makes it very much easier to move servers between machines
without confusing people.
So, for example, a research project with its own disk will get its
own server, and if I later move the disk, the users never need know.
The option is being able to specify an alternative port as a flag to
afpd sounds good, especially if the actual port number was an option -
rather than hardwiring these numbers into start-up files.
In fact, what I would really prefer would be if afpd could create
multiple servers based on a configuration file. This configuration
file would specify the "master" server with the constant port number,
and have slots where afpd might write in the current port number chosen
for other servers.
A bit like the atalkd.conf and papd.conf files.
A related aside, does anyone know the truth behind the claim on
"www.macintouch.com" today (11th) that the AppleShare Client 3.7
can only talk to one IP server per subnet? (Which would make this
entire discussion pointless.)
Cheers,
Duncan.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:36 EST