[FreeNX-kNX] sleeps in freenx code

[Sunil]

user's home is on nfs but I have setup a 'fake'
(node.conf style) home for him on a non-nfs local
partition.

why should the machine architecture or even NFS be a
problem with a piece of software? Sleep times can vary
considerably between machines  and that's exactly why
one should avoid using sleeps as means of waiting for
something to have successfully completed or done
something. Particularly locally, when you have other
more reliable means of synching.

And since the patches for nxnode/nxserver make my
reconnection work, that is a proof that the times put
in by default there are not long enough for many
setups.

-Sunil

--- Thorsten Sandfuchs <fux at users.berlios.de> wrote:

> On Fri, Jul 29, 2005 at 08:49:42AM -0700, Sunil
> wrote:
> > After much fiddling for failed resumes, I realised
> > that the timeout values may be too small in
> certain
> > places. My resume works everytime if I have these
> 
> could you please be a little bit more verbose on the
> background architecture
> of the machines with and without the problems. Is
> there NFS involved? In the
> home, whole file-system? Whats the performance of
> the underlying systems?
> 
> greetz,
> 				/fux
> -- 
> 
> Thorsten Sandfuchs  ***  
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> 



		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs