[FreeNX-kNX] Re: floppy, cdrom access for roaming users

[Fabian Franz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Donnerstag, 27. Januar 2005 15:59 schrieb Chris Fanning:
> > > ..to node_startsession()
> >
> > I think we still have a problem with reconnection, as I'm taking the
> > stored IP from the stored sessionfile, which might be wrong.
> >
> > Can you confirm this bug?
> [...]
>
> Display Username        Remote IP       Session ID
> ------- --------------- --------------- --------------------------------
> 1000    chrisf  192.168.10.23   070697293AA69E831AA08F5FB7A5EFE3
> 1000    chrisf  192.168.10.20   2A58CEA8EB16D5F7E7A7B0985F417B2A
> 1000    chrisf  192.168.10.22   3C4D4685D250A9BDCEFBD3F76B9BD992
> NX> 999 Bye
>
> So it seems that the update of ip's are correct but expired sessions
> are reported leading to confusion.

Yes, there might be still a bug somewhere.

No I mean something different:

You are sitting at machine:

192.168.0.1 and start a session:

NXUSERIP=192.168.0.1

and smb://$NXUSERIP/fd does work and you are happy.

Now you detach from your work by suspending the session.

You move to another machine and resume the session from:

192.168.0.2

But $NXUSERIP is still: 192.168.0.1 and even nxserver --list lists still 
192.168.0.1 (according to the Code)

So you can't access your local floppy drive.

The sessionid will remain the same in a suspend/resume situation.

So the added complexity allows suspending/resuming session with automatic 
update of the .desktop files.

Or how would you do that in this situation?

I think we need to define a "resume"-script or something like that, which is 
run when the user resumes a session.

cu

Fabian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB+QIpI0lSH7CXz7MRArhcAJ9clVWi9WCLs+RQTYwi5wTHW9pO1wCaAsyH
BmPm3L/EWk5y+glt6O5xCFM=
=Z/Pe
-----END PGP SIGNATURE-----