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:from:content-type:content-transfer-encoding :mime-version:subject:message-id:date:cc:to; q=dns; s=default; b= pdd003L5A+TgFMNNbqM4hvAPPmIlsV5D+LGXuz0N+XAvOYjUDbhUPumMBoho5UuH wI8u36Sn06bfy+O1UkT5rysiRAqmM7fCwszKZp2K/lgfsag8JYHCkjFebfVqrpa9 p5cGs0tXP5G1LrBhvtpBqFea774mqRefHRzIqnne1+k= 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:from:content-type:content-transfer-encoding :mime-version:subject:message-id:date:cc:to; s=default; bh=mtqOr 0cxCjYaw0RuH/ihbKXS0Zg=; b=UmoMdeqgz0QwMtcNR8BYo0MqQ1DEVaYUUwWdr kkXCB5K4hUCo0ngneqkABSnPNysSR2UF94GzMU1HvDGE0rpg2betunxms9yWRP0g xrNUKKsgemYeQ2xMa+DNoOdSnadxYktSVVZvjZhtJt0evHA02Mi7WTazn3jVA6nJ bgWKFA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL autolearn=no version=3.3.1 spammy=H*F:U*cygwin, H*r:sk:smtp1-g, H*RU:sk:smtp1-g, HX-Spam-Relays-External:sk:smtp1-g X-HELO: smtp1-g21.free.fr From: Denis Excoffier Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Subject: Searching how to replace dosfilewarning functionality Message-Id: <87A8C69F-2350-4945-981A-2CD2F38E9F5F@Denis-Excoffier.org> Date: Wed, 29 Jan 2020 23:48:36 +0100 Cc: Denis Excoffier To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 00TMnaxa005504 Hello, I see (https://cygwin.com/ml/cygwin-cvs/2020-q1/msg00042.html) that the Cygwin code that handles the dos_file_warning option will be removed soon. I use this option. I don’t use it directly (for DOS paths) but as a signal to be sure that no Cygwin process remains present on my system. This is useful in some cases (re-reading /etc/passwd, /etc/nsswitch.conf occurs only for the first process) but also mainly to make sure that if my PC uses memory or CPU at 100%, Cygwin is not the culprit (since no Cygwin process remains loaded). I don’t use cygrunsrv or equivalent. I do this: 1) I replace "bool dos_file_warning;" with "bool dos_file_warning = true;", and recompile cygwin1.dll. This has to be done at a regular basis, at each new version or snapshot. 2) In my .cshrc i install "echo \\ /nonexistent*" (or something more clever, like "echo \\ /nonexistent* |& head --lines=-6"). 3) When I login, if I see "Cygwin WARNING:", this means that apart from the current process, there is no other Cygwin process in my system. An important feature is that the "Cygwin WARNING" message never appears afterwards (in subsequent shells, like in xterm’s). 4) If I exit from a shell that has displayed "Cygwin WARNING:", I’m sure that no Cygwin process remains (I know that my .cshrc is clean about process creation etc.). Is there any alternative to this almost-functionality if this code is removed? Regards, Denis Excoffier. -- 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