public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: network trace capturing tool in cygwin
Date: Wed, 19 Jun 2019 18:19:00 -0000	[thread overview]
Message-ID: <69d2f08c-fccb-7bc5-3be4-0c185e1a9ec9@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB7PR01MB5386D906B79C08B568B30E9DDEEA0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>


On 2019-06-18 12:27, Jose Isaias Cabrera wrote:
> Andrey Repin, on Tuesday, June 18, 2019 02:09 PM, wrote...
>> If that software is required for your work, they have no other way than to
>> let you use it.
>> If they actively deny you the working environment, find a better job.
> That's the easy way out. ;-)  Thanks.

Seriously, if an org won't let you have the tools to diagnose or fix a problem,
then as you can not help with the problem, it's not your problem, it's for
someone else to deal with.
You can not do everything, and if they can pay people to enforce blocks to
prevent work, they can pay to diagnose problems for which you have neither tools
nor experience.
The solution may have to be political, to buy a commercial tool e.g
	https://www.paessler.com/network-analyzer-diagnostics
or hire consultants to provide and use said tools.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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

      reply	other threads:[~2019-06-19 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 17:02 Jose Isaias Cabrera
2019-06-13 17:27 ` Pokechu22
2019-06-13 17:40   ` Jose Isaias Cabrera
2019-06-18 15:35 ` Andrey Repin
2019-06-18 16:54   ` Jose Isaias Cabrera
2019-06-18 18:20     ` Andrey Repin
2019-06-18 18:27       ` Jose Isaias Cabrera
2019-06-19 18:19         ` Brian Inglis [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=69d2f08c-fccb-7bc5-3be4-0c185e1a9ec9@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).