[FreeNX-kNX] Resuming suspended sessions : Still not working]

[Rob Thomas]

Hi Rick,
I've knocked up a workaround script until this suspend\resume bug is
fixed. You will need to cron to run quite frequently, think we're
running it every 5 minutes. I'm not a scripting expert btw.

*****************************
#!/bin/bash
# Fixes the geometry parameter in the session file so that it can be
resumed : workaround until session resuming is fixed
nxgeofixver=1.0
#echo nxgeofix v$nxgeofixver : Fixes the geometry parameter in the
session file so that it can be resumed

NXSessDir=/var/lib/nxserver/running

for sessfile in $(ls $NXSessDir)
do
	[ $(grep -c geometry=fullscreen $NXSessDir/$sessfile) -ne 0 ] &&
line=$(grep screeninfo $NXSessDir/$sessfile|grep -v fullscreen) ||
line=""
	if [ X$line != X ]
	then
		grep -v geometry=fullscreen $NXSessDir/$sessfile > $NXSessDir/$sessfile.tmp
		echo geometry=$(echo $line|cut -d"=" -f2|cut -d"x" -f1)x$(echo
$line|cut -d"=" -f2|cut -d"x" -f2) >> $NXSessDir/$sessfile.tmp
		chown nx.nx $NXSessDir/$sessfile.tmp
		mv -f $NXSessDir/$sessfile.tmp $NXSessDir/$sessfile
		echo $(date) $(echo $HOSTNAME|cut -d"." -f1) nxgeofix v$nxgeofixver
: Fixed session $(grep sessionId= $NXSessDir/$sessfile|cut -d"=" -f2)
for user $(grep userName= $NXSessDir/$sessfile|cut -d"=" -f2) >>
/var/log/nxgeofix
	fi
done
exit
*****************************

Cheers
Rob
On Wed, 29 Dec 2004 11:04:07 +0800, rick <rick at mcc.mod.net.ph> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> are we able to solve the problem when resuming sessions?
> 
> i have the following on debian:
> 
> nxagent  1.4.0-final-1
> nxlibs   1.4.0-final-1
> nxproxy  1.4.0-final-1
> nxserver 0.2.7-1
> 
> i encounter failure in resuming session in any display area set on the
> nxclient (1.4.75).
> 
> as encountered by others, when i edit
> /var/lib/nxserver/running/sessionId\{475BB39F9E01F070EE5768B25ACD4EBC\}
> 
> and change the geometry to 800x600, i am able to resume the session
> successfully. is there a way to automate this?
> 
> thanks... we've been using freenx since september with 15 users
> accessing simultaneously...
> 
> Rick Stout wrote:
> |
> |
> | Rob Thomas wrote:
> |
> |> Another question, should the versions of the nx package rpm you've
> |> created on your site follow the version of what has been released by
> |> No Machine as in the server version? Or put another way do No Machine
> |> release the GPL equivalent code for the nx packages for each drop of
> |> their commercial server version?
> |
> |
> | When I started building the packages, they were correspondent with the
> | 1.4.0 snapshots, so I used the snaphot name, then the final number
> | (1,2,3) was the version of the package. Future package revisions will be
> | named a little better. Rpm building was a new experience for me.
> |
> | Regards,
> |
> | Rick Stout
> | _______________________________________________
> | FreeNX-kNX mailing list
> | FreeNX-kNX at kde.org
> | https://mail.kde.org/mailman/listinfo/freenx-knx
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
> 
> iD8DBQFB0h6nIDNE4MKx5kMRApK2AJ9y08ri/Kh0TlK4c1r7VuEgqKyKgACgkBbT
> s2+TN/II096+4/PjVYnOAEU=
> =SqC3
> -----END PGP SIGNATURE-----
> **************************************************************************************************
> The contents of this email and any attachments are confidential.
> It is intended for the named recipient(s) only.
> If you have received this email in error please notify the system manager or  the
> sender immediately and do not disclose the contents to anyone or make copies.
> 
> ** eSafe scanned this email for viruses, vandals and malicious content **
> **************************************************************************************************
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>