[FreeNX-kNX] problems near the end of connect w/freenx client with fc5 on both machiens

[Terje Andersen]

On Tuesday 28 March 2006 19:01, John H. wrote:
<snip>

> #########################################################################
> # Logging directives
> #########################################################################
>
> # This directives controls the verbosity of the server-wide log.
> # 0: No Logging
> # 1: Errors
> # 2: Warnings
> # 3: Important information
> # 4: Server - Client communication
> # 5: Information
> # 6: Debugging information
> # 7: stderror of some applications
> #NX_LOG_LEVEL=0

Try uncommenting the line above and set it to NX_LOG_LEVEL=1

<snip>

> # Before turning logging on, please make sure that NX_LOGFILE is
> # writeable for the "nx" user
> #NX_LOGFILE=/var/log/nxserver.log
Check that the file above actually exists and check that the it's writeable to 
the 'nx' user.

> # This directive controls if the temporary session directory
> # ($HOME/.nx/C-<hostname>-<display>-<session_id>) should be kept after a
> # session has ended. A successfully terminated session will be saved as
> # T-C-<hostname>-<display>-<session_id> while a failed session will be
> saved # as F-C-<hostname>-<display>-<session_id>.
> # The default is to cleanup the directories.
> #SESSION_LOG_CLEAN=1

Uncomment the line above and set it to "0". This will ensure that the logs for 
the failed sessions are kept after the session is terminated. 

You can then log in and after the session terminates you can check the logs in 
the directory specified in the description above.

You will then have two places server-side with logs to check out. On the 
client side you should find logs in the users homedirectory.

	/Terje