public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Michael McMahon <michael.x.mcmahon@oracle.com>
Cc: cygwin@cygwin.com
Subject: Re: Problems with native Unix domain sockets on Win 10/2019
Date: Fri, 25 Sep 2020 12:32:05 -0400	[thread overview]
Message-ID: <ee8eb6dc-51e1-7a73-04ef-14a7baeaa641@cs.umass.edu> (raw)
In-Reply-To: <f6ebc8f3-d57e-3fd1-14db-8f231bdb39e0@oracle.com>

On 9/25/2020 12:13 PM, Michael McMahon wrote:
> We're just trying to compile a test case and I checked that the
> command line I sent does work. So, I think that it okay.
> But, the original problem is with the Cygwin command line tools.

Well, it's not a problem with the tools (IMO), it's that the particular Linux program you're 
interested in has not been ported to Cygwin.  It's not unusual that Linux programs need at least 
some adjustment to their build process in order to work - sometimes the adjustment is larger than 
others, and some things make such deep assumptions about Linux that it is not practical to port 
them.  That may be the case here.

Someone who knows more about Samba, how it is supported on Windows, and the limitations of Cygwin 
w.r.t. Samba may be able to say more.  If there's a Windows command line tool, you can invoke it 
from Cygwin (as I previously pointed out).

Just trying to help get you to the place where you can run a command to shutdown / restart a Samba 
remote ... Does it have to be exactly the "net" program from Linux?

Best wishes - EM

  reply	other threads:[~2020-09-25 16:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 11:25 Michael McMahon
2020-09-24 11:26 ` Ken Brown
2020-09-24 12:01   ` Michael McMahon
2020-09-24 17:11     ` Brian Inglis
2020-09-25 13:19     ` Ken Brown
2020-09-25 14:29       ` Michael McMahon
2020-09-25 14:37         ` Eliot Moss
2020-09-25 16:13           ` Michael McMahon
2020-09-25 16:32             ` Eliot Moss [this message]
2020-09-25 18:50         ` Ken Brown
2020-09-25 20:30           ` Ken Brown
2020-09-26  0:31             ` Duncan Roe
2020-09-26  1:22               ` Ken Brown
2020-09-26  7:30             ` Michael McMahon
2020-09-28 11:03               ` Michael McMahon
2021-01-30 16:00                 ` Ken Brown
2021-01-31 23:30                   ` Michael McMahon
2021-02-01 15:04                     ` Ken Brown
2021-02-01 15:10                       ` Corinna Vinschen
2021-02-07 19:35                         ` Michael McMahon
2021-02-08 15:30                           ` Ken Brown
2021-03-16 11:06                             ` Sv: " sten.kristian.ivarsson
2021-03-16 13:00                               ` Michael McMahon
2021-03-16 15:19                                 ` Ken Brown
2021-03-17 12:47                                   ` Sv: " sten.kristian.ivarsson
2021-03-17 15:47                                     ` Ken Brown

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=ee8eb6dc-51e1-7a73-04ef-14a7baeaa641@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    --cc=michael.x.mcmahon@oracle.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).