I've got a couple of GGUX 2.1 servers and a few users have complained about the lsession log files in their home directories. They are also concerned about the log files containing key stroke information.

How can I either turn off the logging or tune it to not record the key strokes?

Cheers

Cliff

QUOTE:
How can I either turn off the logging or tune it to not record the key strokes?

If you look near the top of $GOGLOBAL_ROOT/bin/startXgo.sh file, you will see something like this:

Code:

if [ ! -d ${HOME}/.graphon/session-logs ] then mkdir -p ${HOME}/.graphon/session-logs fi if [ -d ${HOME}/.graphon/session-logs ] then tmp_logfile=${HOME}/.graphon/session-logs/goglobal-tmp.$$ else tmp_logfile=/dev/null fi # redirect output to the (temporary) error file # evgenyr: setting the tmp_logfile variable to /dev/null here will disable logging exec 2> $tmp_logfile exec 1>&2

If you set the

Code:

tmp_logfile

variable to "/dev/null" where the "evgenyr: comment" indicates, logging will be disabled, albeit for all users on the machine on which you make this modification. For applications that are started through XDM, the file to edit is $GOGLOBAL_ROOT/bin/startXDM.sh I am not aware of any user-tunable parameters to adjust what Xgo logs. Hope this helps -- Evgeny Roubinchtein

Cliff,

If you really want to disable the session logs, the method that Evgeny suggested ought to work. However, this will also prevent the logging of any messages output by the X clients that are started in the session, and in the case where additional applications are launched into an existing session, the log file may be created (so that the additional clients will be able to log their standard error).

Xgo does not log keystroke information (which would be a huge security ramification and wouldn't make much sense). Do you have a log like that that we could look at? The only possibility I can think of would be a misconfigured keytable that might log exception conditions in key handling. But this would probably be better solved by fixing the misconfiguration than by disabling logging altogether.

The bottom line is that disabling session logs is likely to make it difficult or impossible for you or us to troubleshoot any problems that you might encounter in the future.

Troy

We were able to determine that several foreign language keytables in v2.1 were shipped with a "DEBUG" option included. This option causes each key translation to be logged, effectively logging every keystroke.

More information is available in this thread.

Troy