[FreeNX-kNX] [SOLVED] NXPlayer and FreeNX: Cannot Resume Suspended Session

[Nick Couchman]

>> 
>> So, it looks like FreeNX is delivering the session list to the 
>> client in such a way that it is incompatible with the newer clients.
> 
> Yup
> 
>> Any idea what can be done to resolve this?
> 
> Not much (without knowing what NXPlayer is expecting)

Well, I managed to figure out what NXPlayer is expecting.  First, it seems to be more picky than NXClient about the length of the lines of the sessions that are delivered back by the server.  So, I took a session log from a known working system (running NX Preview) and looked at how the sessions were being delivered.  I noticed that the length of some of the headers had changed, and that they added the Username field at the end.  So, I created a patch for the nxserver shell script from FreeNX that modifies how it delivers those sessions to the client, patched it on a couple of my servers, and it works.  I also kicked of NX Client 3.5 on a client and connected it to the patched server to verify that it doesn't break backward compatibility, and it still works.

I'm happy to contribute the patch to FreeNX, as long as my method of figuring out what NXPlayer wants isn't going to cause any legal issues?  I don't think so - I would think the protocol itself is part of the open source nature of the components, and since it's logging it in plain text, that should be okay, but I wanted to check, first.  Also, should I post that patch, here, or is there a developers list?

-Nick



--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.