Michal Svamberg wrote: > I have a question about this problem, do you consider about new option > with maximum clients with the same UUID that can connected to > fileserver? Or write warning message to FileLog (without debug)? > By my opinion it is not good if clients are able to shutdown a server.
If you have 100 clients with the same UUID as far as the file server is concerned, they are the same client that just happens to be multi-homed with 100 address-port combinations. The whole point of the UUID is to provide a unique identifier for each client. If you are distributing clients that are all manually configured to use the same UUID, that is an administrative problem. The specific problem that you have run into is that your clients have registered more callbacks via FetchStatus calls then can be maintained by the file server in the callbacks table. The file server is therefore searching for a callback that can be deregistered. It doesn't want to deregister a callback from the same host that is attempting to register a new one because doing so could produce a feedback loop. Unfortunately because all of your clients have the same UUID, there is only one host entry and there are no other hosts from which callbacks can be deregistered. The answer is not to place a limit on the number of address-port values that can be associated with a host. Doing so would adversely impact clients behind NATs or that migrate across networks that dynamically assign IP addresses. The answer is to fix the clients. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
