Conference utrop1::linkworks_v3

2206.0. "Affect of powering off client PC when exiting." by KERNEL::uvodhcp74.uvo.dec.com::crooks (A Philly blunt that is!) Wed Apr 23 1997 19:03

Hi,

LNX v3.0.7 on Unix v3.2g Ingres  v6.4 and Wfwg clients. 

Customer has a minor query about the affect on Linkworks
of powering off the client PC whilst the desk is still
being exited. For various reasons (slow network, big database)
when users come to the end of the day and exit their Desks
the time it takes to actually exit can be up to 30 minutes!
As a result users quite often turn off their PCs before it
has completed. This has 2 consequences:

1. When user logs back into LNX they get the message saying
"A user with your name already logged in - log them out?"

2. Once back in the Desk some icons that had been placed in a 
specific location on the desktop (during the last session) are 
no longer in the same place - quite often the icons will be 
sitting on top of each other (ie you can only actually see 
the icon on top). 

This behaviour is most often seen within a set of nested 
Cabinets. 

I have more or less reproduced this behaviour by creating 6
Cabinets each within the other and then creating 4 objects 
within one of the cabinets. If I drag each 1 of the 4 icons
to a corner of the window and then do exit Desk and  immediately
power off my PC and reboot. When I get back in to the Cabinet
the icons are re-arranged in a horizontal line at the top of 
the window as if a Layout - Tidy Window has been executed. (I
think the reason the customers icons are on top of each other 
is because they have set a small value for Horizontal Icon 
Spacing.) 

Their question though is, whether the 'automatic' Tidy Window 
effect is expected behaviour? 
The obvious advice is dont power off early but not so easy to 
stop users doing it....

Any comments.

Alan Crooks UK CSC.

    Alan,
    
    Logout times of 30 minutes are not normal, there used to be a problem in
    LinkWorks 3.0.7 and Ingres wich was fixed in 3.0.8, and also in a
    special kit for lnx3.0.7.
    This fix was made for a customer who was suffering from a similar
    problem ( need to investigate if we still have the fix some where for 
    3.0.7).
    
    Han
    
     

    Alan,
    
    location of patch: DISK$LNX:[KITS.PATCHES.307.OSFING]
    
    
    Han

Hi Han

Thanks for looking at this one. 

Any fixes welcomed.

speak to you soon

Alan.