Subject: Re: 1.99gb window limit
From: jeff b (jeff@univrel.pr.uconn.edu)
Date: Tue Oct 03 2000 - 12:07:05 EDT
Basil Hussain wrote:
> > Just to chime in, but I have the similar problem with only seeing a
> > 1.99gb window on my server's true size - this is with 1.499 from
> > SourceForge.
>
> Yes, this indeed appears to be a bug or misconfiguration. I have just
> installed netatalk-1.4.99-0.20000927mdk on RedHat 6.0 from the RPM on
> SourceForge and I'm getting the same thing.
It was my understanding that the 1.9 GB display problem was related to
the version of Appleshare Client that you are using -- the older ones
seem to have that problem.
> Whilst I'm on the subject of 1.4.99, I have a few suggestions for the
> default config supplied with it.
>
> In afpd.conf it indicates that the default config for file sharing is:
>
> - -transall -uamlist
> uams_guest.so,uams_clrtxt.so,uams_dhx.so -nosavepassword
>
> which seems a bit strange, as I believe that you have to set something
> special up on the Mac side to use DHX. Providing a default of:
>
> - -transall -uamlist uams_guest.so,uams_randnum.so -nosavepassword
>
> would be better, so long as you have OpenSSL installed (the RPM's
> dependencies seem to take care of that anyway). 2-way encrypted
> passwords just work out of the box.
If everyone else is good with the change, we can make it -- I'm just not
sure what people have had success with.
> Also (and this is very strange), ATALK_BGROUND in netatalk.conf is set
> to 'no' by default! I can't imagine any situation (apart from debugging)
> where you would want to run a daemon service in the foreground. Maybe
> this is intentional (as it is beta), but it confused the hell out of me
> for a while.
That setting does not run netatalk in the foreground... it merely causes
the init scripts to run in the foreground. This is important for seeing
whether it starts or fails in Redhat type initscripts.
jeff
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:16 EST