X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:reply-to; q=
	dns; s=default; b=OAlLtuBOVbsrL9a9sGLM0V9IkdiLOmZXT+G20iPLgBOg8V
	+Pmtq0ri7NmkiT7itOtdiZINLggEMQEWG3SPbsbHC3xllCJxT/qah1Jr1OVOCxVG
	pEbBTOIOiOJ/rnpWoXibvAV0j1e5XjSc2NeZAIzOgLC3dl1L/cf/Qzpbnt64k=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:reply-to; s=
	default; bh=sVwG/QWISSwzGz0vnokzZ3RePyE=; b=QGDXy3XXClO4teCRt8KN
	1lhgaNwd+N1z/2ffrW3M1btBsOTbAF1ZUkQUYytiHvGSXNEuxs2RUr6hdD27rR5X
	vvMCqXYwQAWgPUK3H0v9cCBdRxx5cCkuGoeW6eYMWBJWw1IxmKJlu7wknyO27KZl
	orUSFmFz6D1ktqkQG3hNryA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=informing, H*r:Unknown, Emacs, shutdown
X-HELO: blaine.gmane.org
To: cygwin AT cygwin DOT com
From: Will Parsons <varro AT nodomain DOT invalid>
Subject: left-over .serverauth.#### files
Date: Sun, 4 Dec 2016 21:02:50 -0500
Lines: 20
Message-ID: <slrno49imb.2gg.varro@anukis.local>
Reply-To: gyliamos AT gmail DOT com
User-Agent: slrn/1.0.2 (FreeBSD)
X-IsSubscribed: yes

For quite a while, I've noticed an accumulation of .serverauth.####
files on entering a Cygwin environment.  Since it's been only a minor
annoyance, I've dealt with it by running a small script to delete all
but the latest instance.  Finally, though, I thought I should solve
the root problem of why these files were being left over, and started
to investigate.

For some reason, I had always assumed they had something to do with
running Emacs in server mode, but apparently, they have nothing to do
with Emacs, but are a result of not shutting down an X session
"cleanly".  I suppose that's true enough - I don't start X
automatically, and when shutting down, never think to make an explicit
shutdown of X.

It seems like there should be a way of informing X to clean up on
exit, but I'm not sure how.  I'm starting X from a shortcut that runs
startxwin.

-- 
Will


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple