on 28/6/00 5:34 PM, andrew morgan wrote:
> On Wed, 28 Jun 2000, Stephen Welker wrote:
>
>> It appears that atalkd.conf gets rewritten by netatalk.
>>
>> For example my atalkd.conf file originally had...
>>
>> ne1 -phase 2 -zone "printing"
>> rl0 -phase 2
>>
>> but after a reboot it became...
>>
>> ne1 -phase 2 -net 65280-65534 -addr 65280.83
>> rl0 -phase 2 -net 65280-65534 -addr 0.0
>
> It will rewrite it unless you use -seed, like so:
>
> ne1 -seed -phase 2 -net 1-10 -addr 1.1 -zone "printing"
> rl0 -seed -phase 2 -net 11-20 -addr 11.1 -zone "otherzone"
>
> If you don't use -seed, it will ask the appletalk network for the correct
> settings. If there is no other appletalk router (which appears to be the
> case above), then it comes up with some defaults.
Andy
Thanks for your reply.
Was it a decision by the original netatalk architects to have the software
rewrite the config file?
Is there a way to disable netatalk modifying the config file?
Why couldn't netatalk simply report an error in a log file and allow the
sysadmin fix it as they please?
The current/default situation is confusing to say the least. Especially when
you are debugging one configuration and netatalk is giving you another!
This gets even more confusing when dealing with seeded versus non-seeded
networks, (sometimes an easy network requires some clever magic ;-) ever
tried to switch between seeded and unseeded?
I gather by your response that only the "seeder" is the only node that is
permitted to set a zone name?
Please excuse my novice AppleTalk expertise - I am used to plugging a few
Macs & printers together - of course they work! However, I am trying to
configure two independant networks on one host, as mentioned in my original
post.
--
Stephen Welker
