We recently had this problem on a replicated volume.
Setting the server prefs such that the other server
would be consulted, cause the IP acl to be noticed
immediately. Before that, we waited for 24 hours for
the change to take effect. We also have an open problem
report for this problem.
> [EMAIL PROTECTED] writes:
> >
> [...]
> > >>Once the fileserver has been restarted, IP ACLs work fine.
> > >>
> > >>Add a new IP address, and you have to restart your fileservers.
> > >
> > >Yeah - I have no idea why I need to restart my fileserver. I didn't
> > >know that I needed to - I guess that I just restarted it conveniently
> > >when I added the IP addresses. Anyhow, maybe Transarc can comment on
> > >other ways to deal with this?
> >
> > You can also wait 2 hours for the fileserver to refresh the knowledge
> > of the newly added IP addresses
> >
> > Dawn
> > File Systems Support
>
> We waited, and waited, and several days later, still no go.
>
> We filed an incident report a while ago.
>
> < Paul
...Tim
Tim Theisen Associate Researcher
Internet: [EMAIL PROTECTED] Department of Computer Sciences
UUCP: uwvax!tim University of Wisconsin-Madison
Phone: (608)262-0438 1210 West Dayton Street
FAX: (608)262-9777 Madison, WI 53706-1685
