public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Denis Excoffier <cygwin@Denis-Excoffier.org>, cygwin@cygwin.com
Subject: Re: Searching how to replace dosfilewarning functionality
Date: Thu, 30 Jan 2020 07:20:00 -0000	[thread overview]
Message-ID: <1069298224.20200130100621@yandex.ru> (raw)
In-Reply-To: <87A8C69F-2350-4945-981A-2CD2F38E9F5F@Denis-Excoffier.org>

Greetings, Denis Excoffier!

> 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?

I fail to see why you want to do such mental gymnastics.

Just create a script like

  test $( ps -al | grep -vE "\<${TTY##/dev/}\>" |& wc -l ) -gt 1 && {
    echo There\'s likely other processes running from Cygwin environment.
    echo Please stop them or use --force to suppress this test.
    exit 1
  }

and run it whenever you suspect Cygwin tasks running in background.

[C:\arc\cygwin\install]$ install-cygwin.sh
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
     1563       1    1563     187240  ?             18   Jan 29 /usr/bin/cygrunsrv
     1562       1    1562     187172  ?         197608   Jan 29 /usr/bin/ssh-pageant
     1564    1563    1564     190868  ?             18   Jan 29 /usr/sbin/cygserver
There's likely other processes running from Cygwin environment.
Please stop them or use --force to suppress this test.


-- 
With best regards,
Andrey Repin
Thursday, January 30, 2020 10:03:02

Sorry for my terrible english...
--
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


      parent reply	other threads:[~2020-01-30  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 22:49 Denis Excoffier
2020-01-30  5:09 ` ASSI
2020-01-30  7:20 ` Andrey Repin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1069298224.20200130100621@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@Denis-Excoffier.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).