------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=81369        




------- Additional Comments From Russell.J.LeBar erac com  2004-12-01 00:34 -------
Note: I am not doing my own locking. Based on the user's environment and possilbly some xprop -root output I either do nothing, run a command to disconnect the user's thin client session, or run the original kdesktop_lock binary. My main concern is that I want to be able to do this without having to rename kdesktop_lock, copy my wrapper in, and then try and rembmer to recopy the files back in if a I do gmake install again for kdebase. 


Give me a config file for kdesktop_lock that lets me specify an external program to execute and then specify what to do based on the return code. For example:

[External Command]
Command=/erac/bin/kdesktop_lock.pl

[Return Code 0]
Operation="lock"

[Return Code 1]
Operation="do nothing"

[Return Code 2]
Operation="command"
Command="/opt/SUNWut/bin/utdetach"


For the curious here is my wrapper script:

#!/usr/local/bin/perl
# Since all of our ICA clients are running under some other OS/desktop
# what is the point of running a screensaver in an ICA session!?!
exit 0 if exists $ENV{CITRIX_SESSION_ID};
if( exists $ENV{SUN_SUNRAY_TOKEN} ) {
        my $xprop = `/usr/openwin/bin/xprop -root _SUN_SUNRAY_CONN_INFO`;
        # Disconnected session so no need for a screensaver
        exit 0 if $xprop =~ /PN=-1 PAD= PPN=-1/; 
        # Active session so disconnect it instead of locking it
        exec '/opt/SUNWut/bin/utdetach' if( 
             $ENV{SUN_SUNRAY_TOKEN} =~ /(^auth\.)|(^escape\.)/ );
        }
# Run the real kdesktop_lock
exec "$ENV{KDEDIR}/bin/kdesktop_lock.orig --forcelock";