[FreeNX-kNX] Disable shared memory and shared pixmap

[chris at ccburton.com]

Julio Carlos Barrera Juez <juliocarlos.barrera at grupoica.com> Sent by: 
freenx-knx-bounces at kde.org

Hi cb!

'lo Julio

 
Thank you for your response.
 
I’m using a freeNX server on an Ubuntu machine and a freeNX client on an 
Ubuntu machine. I’m testing nxproxy and nxssh command line binaries, I’m 
not using nxclient or other GUI NX clients at all. I want to disable 
shared memory and shared pixmap features using these client binaries and 
without modifying the server. When I want to establish a session I use 
nxssh binary to provide command line input like these:
 
$ nxssh -i  key nx at server_machine –B
> login
> user
> password
> startsession --link="lan" --imagecompressionmethod="-1" 
--type="unix-application" --application="xeyes" --encryption="0" 
--noshmem="1" --noshpix="1"
 
After a few seconds the sessions is created and I use cookie and port to 
create the remote connection using nxproxy binary in another console like 
this:
 
$ nxproxy -S server_machine:provided_port cookie=provided_cookie
 
It works at all!
 
But I want to disable shared memory and shared pixmaps features, because 
I’m experimenting with a different local X server. I have tried many 
different options in startsession line like:
 
--noshmem="1" --noshpix="1"
 
or
 
--shmem="0" --shpix="0"

*****   These are hard-coded ( back )  to 1 in nxnode  ********

 
But every time I get lines of nxproxy client binary like this:
 
Info: Using shared memory parameters 1/2048K.
 
I have never achieved not using shared memory or shared pixmap. I want 
just it without modifying any source code or binary, just using 
startsession commands using nxssh established session. Any idea?
 
Thank you for your time!


Well if you want that
then
you either need no shared memory available in X
or
you need to set

        shseg=0

for nxnode, in addition to shmem and shpix.


Nomachine set it via "ProxyExtraOptions" node.conf

FreeNX has
           PROXY_EXTRA_OPTIONS

 but it is only invoked for 

        "nxproxy single application mode session" 

which appears to be a rootless non rootless session type !!
        ( I have never used it ( or looked at it ) )

The easiest way (for a live environment) to set shseg is via

          nxacl

so you can choose who gets the benefit

*** BUT***

you still NEED to mod nxnode to get it to send it to nxagent.


For your experimentation you can just add

        shseg=0
after the getparam

Attached here is a .diff of nxnode against some ubuntu .deb I found  for 
you to try


Let us know how you get on . . . . 















-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20121102/c47b5109/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freenx-server_0.7.3.zgit.120322.977c28d-0~ppa11_i386.deb-nxnode-shmem.diff
Type: application/octet-stream
Size: 2227 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20121102/c47b5109/attachment.obj>