From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18915 invoked by alias); 16 Dec 2014 23:39:08 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 18904 invoked by uid 89); 16 Dec 2014 23:39:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yh0-f45.google.com Received: from mail-yh0-f45.google.com (HELO mail-yh0-f45.google.com) (209.85.213.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 16 Dec 2014 23:39:05 +0000 Received: by mail-yh0-f45.google.com with SMTP id f10so6614144yha.18 for ; Tue, 16 Dec 2014 15:39:03 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.170.56.23 with SMTP id 23mr32811816yky.111.1418773143770; Tue, 16 Dec 2014 15:39:03 -0800 (PST) Received: by 10.170.233.6 with HTTP; Tue, 16 Dec 2014 15:39:03 -0800 (PST) In-Reply-To: References: <548C82A3.9080604@gmail.com> <54905E8F.40809@ucsd.edu> Date: Tue, 16 Dec 2014 23:39:00 -0000 Message-ID: Subject: Re: startxwin.exe no longer exists? From: Erik Soderquist To: cygwin-xfree@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00042.txt.bz2 > Apparently not. If I start an X session (using the standard menu item > under the start menu) and manually shut it down, the lock file is not > deleted. On a clean shutdown, the process should clean up its lock files; if it isn't, that needs to looked at and/or reported. The only caveat to that I'm aware of is if a debug flag is set, files the process uses may be intentionally left behind. However, it doesn't sound like you would be setting such flags. >> I actually have no experience with startxwin; I always called the X >> server directly with the options I wanted. > > What do you mean "directly"? From a mintty or such? Windows .bat/.cmd files, custom crafted shortcut on the desktop, windows registry changes... depends on the situation. The one I referenced with the dumb terminals and flaky power is a registry call in autorun starting a .cmd file. >> However, I can say that freeing of lock files is the job >> of the process that created the lock files. If you kill >> the process, stray lock files are a normal expectation. > > No they're not, unless you restrict "kill" to mean "kill -9" or > equivalent. If you kill a process using just "kill", or by shutting > it down normally, it should clean up its lock file. My apologies; I was only considering kill -9 as 'kill the process'. You are correct, kill -15 is also a kill, but should allow the process to exit cleanly. >> ... bringing the X system more in line with general X and > *nix standards, which, as far as I know, has always >> been a general goal of the entire Cygwin set of projects. > > Then it's not succeeding. Shutting down X normally under *nix does not > result in left-over lock files. I will certainly agree that shutting down X cleanly should not leave stray lock files behind. I can also say that I'm not experiencing that issue. My best guess (and this is only a guess) is that something is causing X to crash as it shuts down on your system, causing the lock files to be left behind. -- Erik -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/