On Wed, 5 Jul 2000, Aaron Levitt wrote:
> I tried this on a different server that hasn't been implemented
> company-wide yet, but has the same version of netatalk on the same OS.
> It returned the correct value:
>
> Shutting down AppleTalk services: [ OK ]
> Starting AppleTalk services: (backgrounded)
> Max clients: 120
>
> I will try this tonight when there aren't any users that will be
> disconnected when I restart atalk. Should this have the same result,
> would I need to recompile with the options->connections set to the
> desired number??
That would be one way to fix it. Or you could just hardcode the
connection limit value in your startup script (-c 120 instead of -c
${AFPD_MAX_CLIENTS}). But really, this is just a problem with the startup
script.
> Also, I am aware of the -c flag, but the other server is using a
> afpd.conf file. How can I set the max connections in afpd.conf??
> There doesn't seem to be an option listed for that flag.
The netatalk.conf file is only used by the startup script (typically
/etc/rc.d/init.d/atalk in redhat installs). It sets some shell variables
which the script passes as command-line arguments to afpd, papd, etc.
afpd.conf is read by afpd only after it has started. I don't believe you
can use afpd.conf to set the connection limit. The afpd code suggests
that the command-line option -c is the only way to change this.
Maybe this wasn't entirely clear, but the connection limit is only read
when you start netatalk services. Changing the setting in netatalk.conf
while it is running will not change anything. Just in case you didn't
realize that...
Andy
