about summary refs log tree commit diff
path: root/group.c
diff options
context:
space:
mode:
authorokan <okan>2013-10-25 19:46:16 +0000
committerokan <okan>2013-10-25 19:46:16 +0000
commit6e17b41f566865629d3dd35a6a60e081e6e2b089 (patch)
tree936ef98f0d1f8a5c6293e010a40fc9059c24ab4e /group.c
parent6867821abefd761a840befcfee5a1f1f2fef9831 (diff)
downloadcwm-6e17b41f566865629d3dd35a6a60e081e6e2b089.tar.gz
cwm-6e17b41f566865629d3dd35a6a60e081e6e2b089.tar.xz
cwm-6e17b41f566865629d3dd35a6a60e081e6e2b089.zip
A client_delete should behave differently depending on whether the
triggering event was unmap (with pending destroy) log destroy; we only
need to grab/ungrab the server lock, set WithdrawnState and
XRemoveFromSaveSet clients coming from an unmap event - doing so for
clients coming from destroy are already gone, hence we generate errors.
Diffstat (limited to 'group.c')
0 files changed, 0 insertions, 0 deletions