From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: Cees Dam <Cees.Dam@planet.nl>, cygwin@cygwin.com
Subject: Re: XWin -silent-dup-error does not work anymore
Date: Tue, 02 Jun 2015 17:45:00 -0000 [thread overview]
Message-ID: <556DEBAC.5040603@dronecode.org.uk> (raw)
In-Reply-To: <3485.50957064635$1430414419@news.gmane.org>
On 30/04/2015 18:19, Cees Dam wrote:
> I work as system administrator at the Rotterdam Port Authority. One of the main systems is a huge Vessel Traffic System build of more then 100 Suse Linux
> Systems. About half of the processors is used to display the harbour of Rotterdam with al the vessels (retrieved from 41 RADAR stations) and AIS.
> All the network traffic within this system is based on multicasting.
>
> However, on a few locations like the office of the Pilots, firewalls prevent the multicasting traffic. So I installed a couple of Win 7 systems at there office with Cygwin. With X over ssh I deliver them the same display (application) as on the Traffic centers. Cygwin is installed with only xinit and openssh.
>
> These people are not familiar with computers so I gave them one link on there desktop starting XWin and the ssh connection (mintty -e etc). If they want to start the session again (because they were unaware of the fact a session was already running) I don't like popups and warnings. They should click the X icon on the taskbar to bring the application back up on there desktop.
>
> In 2014 I build a Cygwin 64 bit version (one of the first 64-bit releases) and this problem did not occur.
>
> So it's important for a friendly way of use for people who don't have any kwowledge of computers.
>
> I hope you can solve the problem.
I uploaded X server 1.17.1-5 packages today.
With those, -silent-dup-error should be working again.
Thanks again for reporting this issue.
> Van: Jon TURNEY [mailto:jon.turney@dronecode.org.uk]
> Verzonden: donderdag 30 april 2015 13:10
> Aan: Cees Dam; cygwin@cygwin.com
> Onderwerp: Re: XWin -silent-dup-error does not work anymore
>
> On 25/04/2015 09:32, Cees Dam wrote:
>> If Xwin.exe is started with -silent-dup-error flag and a second
>> instance of Xwin.exe is also started with the -silent-dup-error flag a
>> pop-up notification shows up with fatal errors. The output in the
>> terminal (with -silent-dup-error flag) is the same as shown below with the -v flag.
>
> Thanks for reporting this.
>
> It seems that this has been broken for almost 2 years, so perhaps this option is not often used :D
>
> I'd be interested to hear what your use case is for it?
>
> I'll have a go at fixing it, but it seems there is an interaction now with the '-nolisten tcp' default which makes this not quite straightforward.
--
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
next prev parent reply other threads:[~2015-06-02 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17839.6935262301$1429950806@news.gmane.org>
2015-04-30 11:10 ` Jon TURNEY
2015-04-30 17:19 ` Cees Dam
[not found] ` <3485.50957064635$1430414419@news.gmane.org>
2015-06-02 17:45 ` Jon TURNEY [this message]
2015-04-25 8:32 Cees Dam
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=556DEBAC.5040603@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Cees.Dam@planet.nl \
--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).