From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39669 invoked by alias); 12 Sep 2016 04:20:41 -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 39596 invoked by uid 89); 12 Sep 2016 04:20:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*RU:64.59.136.137, Hx-spam-relays-external:64.59.136.137, WOW, Commands X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.137) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 12 Sep 2016 04:20:29 +0000 Received: from [192.168.1.100] ([174.0.238.184]) by shaw.ca with SMTP id jIjKb3dRPgdaljIjLbCVGQ; Sun, 11 Sep 2016 22:20:28 -0600 X-Authority-Analysis: v=2.2 cv=Q++Q2M+a c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=-60GocgBU46SGeYf_GsA:9 a=PiVldflbWMQk3yRJ:21 a=likkceGZm5YKI5w7:21 a=QEXdDO2ut3YA:10 a=daI9ojH3vpgA:10 a=sRI3_1zDfAgwuvI8zelB:22 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: Commands not working as expected. References: To: cygwin@cygwin.com From: Brian Inglis Message-ID: <0371f378-e11e-5eba-22df-323cd2670023@SystematicSw.ab.ca> Date: Mon, 12 Sep 2016 04:20:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfD1jFDuWQgvIrpqUzu1jKOpzilSIyRYCrdbaQzQxYmxEud5iS0n2H7KwgP7nSr7n+knIrCpboUUtSzjUotH0aRnmkCM8GdjIYFnfV3kc/rxDim6x4IQr NhUJUzBwZSCOyJpWbLfSJ9GGVqS1k8Y3btvt4zmitKzCg6BXhYizn9faFH1C7ecjSPDHtX20aGwJNA== X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00168.txt.bz2 On 2016-09-11 17:03, Brian S. Wilson wrote: > I updated my Cygwin instance to day and ran the date command. For some > reason it spit out only the UTC time, not the EST time and date > information I was expecting. When I ran the "man date" command to see > if anything had changed in the usage, I got the following error messages. > > I tried to update Cygwin again; but got the same results. > > $ man date > 1 [main] man 7788 child_info_fork::abort: C:\cygwin\bin\cygz.dll: > Loaded to different address: parent(0x1E0000) != child(0xB70000) > man: fork failed: Resource temporarily unavailable > > $ man man > 1 [main] man 5524 child_info_fork::abort: C:\cygwin\bin\cygz.dll: > Loaded to different address: parent(0x150000) != child(0xB70000) > man: fork failed: Resource temporarily unavailable You can try running setup, without selecting any packages, to clean up anything left unfinished from the last install, reboot, run setup again with nothing selected, then run mandb under Cygwin to rebuild man db tables. When posting, please at least run uname and post output to show OS and Cygwin platform e.g.: $ uname -srvmo CYGWIN_NT-10.0 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin $ uname -srvmo CYGWIN_NT-10.0-WOW 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 Cygwin Check that setup installs completed properly with: $ ls /bin/*.new ls: cannot access '/bin/*.new': No such file or directory Check that all setup postinstall scripts completed properly with: $ ls /etc/postinstall/[!0z]*.*sh ls: cannot access '/etc/postinstall/[!0z]*.*sh': No such file or directory Check the results of your last setup in /var/log/setup.log.full and for issues in previous recent setups towards the end of /var/log/setup.log. If you're running Cygwin 32 bit (-WOW...i686), you probably ran out of Cygwin address space for rebasing dlls - this may be indicated by the problem with cygz.dll. If you have rebase problems in 32 bit, you can either deinstall some packages, or if you run Windows 64 bit, install a Cygwin 64 bit setup and select the same packages. Please see adjacent FAQ entries 4.44 https://cygwin.com/faq.html#faq.using.bloda and 4.45 https://cygwin.com/faq.html#faq.using.fixing-fork-failures If you still have a problem, please follow the problem reporting guidelines linked below and attach cygcheck output to your reply. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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