* Yann Dirson <[EMAIL PROTECTED]>: > (Oh, I had not noticed that NMU)
Neither did I -- oh, the joy. > That way of fixing the problem seems a bit crude. After all, it may > be legitimate to get the running screensavers to upgrade when the > binary gets updated - but is that what SIGHUP does, I can find nothing > in the manpage or in the README. > > It could be that a correct fix would be to save the current state of > the screensaver before handling the signal, and getting back to that > state afterwards - however that may be more difficult to do safely, > without any time-window kept unlocked. Oh yes. > I'll let you decide, whether to forward this upstream or not. jwz reads this, I guess. But I personally think: Rather NOT kill xscreensaver and thus unlock the screen. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
