From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailsrv.cs.umass.edu (mailsrv.cs.umass.edu [128.119.240.136]) by sourceware.org (Postfix) with ESMTPS id 54A713971C1C for ; Fri, 25 Sep 2020 16:32:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 54A713971C1C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=moss@cs.umass.edu Received: from [192.168.0.16] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 172BD401EB7D; Fri, 25 Sep 2020 12:32:06 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Problems with native Unix domain sockets on Win 10/2019 To: Michael McMahon Cc: cygwin@cygwin.com References: <2b0aeab4-983d-e1d7-301f-edfeeb38cc85@oracle.com> <97d2b3af-224a-6873-fb4a-55a0ae9cd379@cornell.edu> <35426eaa-56ac-ade8-10e1-9f4fd71db609@cs.umass.edu> From: Eliot Moss Message-ID: Date: Fri, 25 Sep 2020 12:32:05 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2020 16:32:07 -0000 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