From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23625 invoked by alias); 8 Sep 2018 00:35:09 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 23612 invoked by uid 89); 8 Sep 2018 00:35:08 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*x:Bat!, H*UA:Bat!, services X-HELO: forward102j.mail.yandex.net Received: from forward102j.mail.yandex.net (HELO forward102j.mail.yandex.net) (5.45.198.243) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 08 Sep 2018 00:35:06 +0000 Received: from mxback4o.mail.yandex.net (mxback4o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::1e]) by forward102j.mail.yandex.net (Yandex) with ESMTP id 6CF0956053F3; Sat, 8 Sep 2018 03:35:02 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback4o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 2pNXik211Q-Z1iaHThS; Sat, 08 Sep 2018 03:35:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1536366902; bh=rWjYnz8BCZJPnsVBj7HULOSPBkKSr/1KwGhrMS/9X0I=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=df74PG1sNjHRJrPwWI8fFN7HHGzeopj6jV2LeeOY+S8kYP1g5qYCgF1657+xJ9BN8 9QYPwEMJPjjYCA87CUktLjKQuGJbw1rBgE54hsDHhLlkUa3n5HX9Yk+5OPOuaXhfUz X34matEw8wcEotAvsbUogU7PyA5YS+ksO14GXwXs= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id CrLO9Q1cWp-Z148VP9w; Sat, 08 Sep 2018 03:35:01 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1536366901; bh=rWjYnz8BCZJPnsVBj7HULOSPBkKSr/1KwGhrMS/9X0I=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=eOrfDO9Nm0Hy9RgChV5w/XpVFmg6URji2Zv5106Fzbw1GQxQHJT/+YC/EjQsGuVzJ NwVU51rujwfZfHlvRu7+2BVHfADQJpb9GXqcqpLwPl50Cr4FVwYze/aG1WXspgZbib coJw+jBdHHrpmGgGZrMVCNorjlz/tJvl/z6q8OJI= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Sat, 08 Sep 2018 00:26:45 -0000 Date: Sat, 08 Sep 2018 00:35:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <1898287098.20180908032645@yandex.ru> To: L A Walsh , cygwin@cygwin.com Subject: Re: continued acl problems In-Reply-To: <5B930505.8000007@tlinx.org> References: <5B92EA14.1030507@tlinx.org> <164180157.20180908002635@yandex.ru> <5B930505.8000007@tlinx.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00140.txt.bz2 Greetings, L A Walsh! >>> In all of these cases it appears that the problem is with directories. >> >>> At first thought it was related to presence of 'TRUSTED USER' >> >>> But I saw some 'flakeyness' on domain ID's, >>> where I saw it display the correct text for them, >>> but scrolling down to look for problems, and back up had the >>> permissions dialog showing the raw numbers for my domain ID's, but >>> scrolling again showed them as Domain\ID. >> >> Do you have cygserver running? > ---- > Well....rt now, not sure...hmmm If you see them in service manager, then I'm curious by your observed behavior. cygserver's one effect is to stabilize SID resolution within a session. And yes, you should not be starting cygserver manually, unless for testing purposes. I have no idea, what effect would have multiple cygserver's running in the same system. > I should have had it running, as it's part of my startXwin.sh > script which I run manually at start of every session, but > did an update and had to kill off most or all of the cygstuff. > But restarted 'X', which used to -- should have restarted > it but, looking didn't see it in process list and trying the > same command manually gave an error: >> cygrunsrv -n -O -S -d messagebus cygserver > cygrunsrv: --neverexits is only allowed with --install > So I look at help and install is for installing a new service > So I look at what services are installed: >> cygrunsrv.exe -L > cygserver > messagebus > syslogd > Looks like the cygserver is already installed... > Looking in the services control panel, I see cygserver, > messagebus and syslogd, but syslogd won't stay running. > Since I just ran the cygrunsrv command above, not sure if that > started it or not. > If I specify two services on the command line, should it > have started both? with the same 'cygrunsrv'? They are set > to start on system boot, but after the cyg-upgrade, they were > likely killed and restarting 'X' likely didn't restart anything > because of the error. > Because cygserver won't let you start syslogd unless stderr > isn't a TTY, I have to send cygserver's error off to /dev/null, > so I wouldn't have seen any errors. > So...am guessing it wasn't running, but may be now (not sure > why syslogd isn't running -- will have to check that out later. > But for now, will have to see if this reoccurs .... > Thanks for the possible cause! ;-) -- With best regards, Andrey Repin Saturday, September 8, 2018 3:23:39 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