Not the same NIC... LDAP server is accessed through a 1GB LAN. bzr is replicating from remote location on a X MB WAN link ( 1 < X < 10 from what I know... ). and that link is not flooded at all... I must admit that the fact that setting up the whoami in .bzr fixed the problem is quite disturbing... Is there anyway I can revert that change ? ( ie removing the ".bzr stored copy" of "whoami output" ? ) then I can test by setting up the user on the local system, so the network is not involved in this anymore. Cheers, -- Alex <div class="gmail_quote">2008/10/31 Matthew D. Fuller <<a href="mailto:fullermd@over-yonder.net">fullermd@over-yonder.net</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Fri, Oct 31, 2008 at 04:53:29PM -0200 I heard the voice of Asmodehn Shade, and lo! it spake thus: <div class="Ih2E3d">> > I really do not think so, since this happens almost everytime after > a big transfer... and the network doesnt break that often. </div>If it's going across the network to look up the user info, and you've flooded the network with bzr data, it might timeout before getting the response. -- Matthew Fuller     (MF4839)   |  <a href="mailto:fullermd@over-yonder.net">fullermd@over-yonder.net</a> Systems/Network Administrator |  <a href="http://www.over-yonder.net/%7Efullermd/" target="_blank">http://www.over-yonder.net/~fullermd/</a>           On the Internet, nobody can hear you scream. </blockquote></div>